n8n_execute_workflow

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits such as whether execution is synchronous or asynchronous, what it returns, or any side effects. For a tool that triggers workflow runs, this lack of detail is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the core action. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's role as an execution trigger with side effects, and the absence of an output schema and annotations, the description leaves critical questions unanswered (e.g., return value, asynchronous behavior, workflow activation requirements). It is underspecified for an agent to use safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with descriptions for both parameters. The description adds a minor clarification ('body directo') about how the payload is sent, but does not significantly augment schema semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Ejecutar un workflow') with a specific verb and resource. It is distinct from sibling tools, which focus on CRUD or listing operations. Mentioning optional input data adds further clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'con datos de entrada opcionales (body directo)' gives context on how the payload is used. It does not explicitly name alternatives, but among siblings it is the only execute tool, making its usage context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.