n8n-mcp

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

No annotations are provided, so the description carries the full burden. It mentions 'Requires write_mode', which adds some behavioral context about permissions. However, it lacks details on what 'stop' entails (e.g., whether it's reversible, immediate, or has side effects), rate limits, or error conditions, which are critical for a mutation tool like this.

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 extremely concise with just two sentences, front-loading the core action ('Stop a running execution') and adding a critical prerequisite ('Requires write_mode'). Every word serves a purpose with no redundancy or fluff.

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 that this is a mutation tool with no annotations, 0% schema description coverage, but an output schema exists, the description is moderately complete. It covers the basic action and a permission requirement, but lacks parameter semantics and detailed behavioral traits, which are important for safe invocation.

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. It doesn't mention the 'execution_id' parameter at all, leaving the agent with no semantic context beyond what's in the schema (just a string title). This is a significant gap for a required parameter in a mutation 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 the verb ('stop') and resource ('a running execution'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_execution' or 'stop_many_executions', which would require more specific context about what 'stop' means versus 'delete' or 'stop_many'.

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 some usage context by mentioning 'Requires write_mode', which implies a prerequisite condition. However, it doesn't explicitly state when to use this tool versus alternatives like 'delete_execution' or 'stop_many_executions', leaving the agent to infer based on tool names alone.

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