Execute workflow

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

With no annotations, the description must disclose behaviors like asynchronous execution, return value (likely execution ID), and prerequisites (e.g., workflow must be active). It only states it triggers execution, omitting important traits.

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?

Very concise (two short sentences) but lacks necessary detail. It is not under-specified to the point of breaking, but missing guidance and behaviors.

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?

For a mutation tool with nested parameters and output schema, the description is too sparse. It doesn't explain execution semantics, error states, or relationship to workflow state.

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 already provided. The description adds 'optionally' for the data parameter, which is helpful but marginal. Adequate for a schema-rich tool.

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 it triggers a workflow execution and optionally sends input data. It uses specific verb 'trigger' and resource 'workflow', distinguishing it from sibling operations like activate/deactivate or read-only tools.

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?

No guidance on when to use this tool vs. alternatives (e.g., n8n_trigger_webhook for webhooks, or n8n_activate_workflow for lifecycle management). The description lacks context for appropriate usage.

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