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: adddescription
inside Input schema FieldsCall n8n workflow tool
node: add ability toinherit
oroverwrite
the decriptionCall n8n workflow tool
node: ifinherit
, 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).