execute_workflow

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

The description goes beyond the annotations by disclosing at-least-once delivery semantics and explicitly warning against blind retries on timeout or network errors. This is valuable behavioral context that the annotations (idempotentHint=false, destructiveHint=true) do not fully convey. It does not contradict the annotations.

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 two sentences, with no redundant words. The first sentence states the purpose, and the second adds a critical operational warning. It is front-loaded and every word earns its place.

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?

The description covers the core purpose and the most important behavioral caveat, but it omits details about the return value or how the workflow's execution status can be tracked afterward. Given the lack of an output schema and the existence of a get_execution_status sibling, this gap makes the tool somewhat incomplete for an agent to use confidently.

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?

With 0% schema description coverage, the description was expected to compensate by explaining the parameters. It mentions 'supplied JSON input' but gives no detail about the structure or content requirements, and it does not describe workflowId beyond what the schema already shows. This leaves the agent with very little semantic guidance.

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 ('Executes a tagged n8n workflow') and the method ('through its webhook using the supplied JSON input'). It straightforwardly distinguishes this from sibling tools like list_workflows and get_execution_status by focusing on execution rather than listing or status retrieval.

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 description makes it clear that this tool runs a workflow, which implicitly signals when to use it compared to the read-only sibling tools. However, it does not explicitly state 'use this when you need to trigger a workflow' or mention any exclusions or alternatives, so it falls short of a 5.

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