n8n-mcp

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a mutation action ('Retry') but doesn't disclose permissions needed, side effects (e.g., overwriting previous attempts), rate limits, or what constitutes a 'failed' execution. The mention of 'load_workflow' hints at versioning behavior but lacks depth on outcomes or constraints.

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 appropriately sized with two concise sentences that are front-loaded: the first states the core purpose, and the second adds a key parameter detail. There is zero waste or redundancy, making it efficient for an agent to parse quickly.

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 a mutation tool with 2 parameters, 0% schema coverage, no annotations, but an output schema exists, the description is minimally complete. It covers the basic action and a parameter nuance, but lacks behavioral context, usage rules, and full parameter semantics. The output schema mitigates the need to explain return values, but overall it's adequate with clear gaps.

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 description coverage is 0%, so the description must compensate but only partially does. It explains 'load_workflow=true' to use the latest workflow version, adding meaning beyond the boolean schema. However, it doesn't clarify 'execution_id' (e.g., format, source) or the default behavior when 'load_workflow=false'. With 2 parameters and low coverage, this is a baseline adequate but incomplete effort.

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 verb ('Retry') and resource ('a failed execution'), making the purpose specific and understandable. It distinguishes from siblings like 'stop_execution' or 'delete_execution' by focusing on retrying rather than terminating or removing. However, it doesn't explicitly differentiate from 'execute_workflow' in terms of re-running versus initial execution.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'load_workflow=true' for using the latest workflow version, but doesn't specify prerequisites (e.g., only for failed executions) or compare to tools like 'execute_workflow' for new runs. This leaves the agent without clear context for selection.

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