Add "description" to Input fields of "When Executed by Another Workflow", to inherit description when using the workflow as AI Agent tool with "Call n8n workflow tool"

[tresorama]

The idea is:

Consider this workflow, with an AI Agent node, that use an other n8n workflow as a tool with Call n8n workflow tool…

Now, you should add fields descriptions in this workflow.

It would be better to define these descriptions inside the invoked workflow (the Tool Workflow)

Feature Description

Details:

• When Executed by Another Workflow node: add description inside Input schema Fields
• Call n8n workflow tool node: add ability to inherit or overwrite the decription
• Call n8n workflow tool node: if inherit, show the inherited deription in the UI

My use case:

AI Agent’s tool reusability

I think it would be beneficial to add this because:

• Better separaion of concern : now you need to edit the input schema also at consumer level (Parent Workflow), not only at server level (Tool Workflow). It’s like the API is fractured between server/client, but should be in server (like MCP Servers).
• Reduce workflow mainteinance: now, when description changes because API changes, you need to edit description in any Parent Workflow that use the other workflow as a tool. These can be a lot of workflows.

Are you willing to work on this?

No, but I can with the DX dicussion. I’m on github (tresorama).

[jimmytacks]

This is the same issue as: Improve AI Agent ‘Call n8n workflow tool’ - Feature Requests - n8n Community

My comment on that thread was:

I have the same issue. Right now every Call n8n Workflow Tool node keeps its own local copy of the Description prompt, so we have to maintain the same text in several places. And that text can be quite substantial (how to format JSON correctly, what parameters to pass in query etc.).

I’d suggest doing something like:

1. Add an optional “Tool description” field to the Execute Sub-workflow Trigger (or Workflow Settings).
2. Make the Call n8n Workflow Tool node pre-populate its Description from that field
3. Warn—or ideally auto-update—caller nodes if the sub-workflow’s description changes later.