n8n-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Requires write_mode', which hints at authentication needs, but fails to describe critical traits like whether deletion is permanent, if it affects associated workflows or executions, error conditions, or rate limits. For a destructive operation, this leaves significant gaps in understanding its behavior.

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 ('Delete a tag') and following with a critical prerequisite ('Requires write_mode'). Every word earns its place, with no redundant or vague language.

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 destructive nature, no annotations, and an output schema (which might cover return values), the description is insufficient. It lacks details on permissions beyond 'write_mode', consequences of deletion, error handling, and how it interacts with sibling tools like 'update_tag' or 'get_tag'. For a delete operation, this leaves too many contextual 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?

The input schema has 0% description coverage, so the description must compensate. It doesn't add any meaning to the 'tag_id' parameter beyond what's implied by the tool name. No details on format, source, or validation are provided. Since there's only one parameter, the baseline is 4, but the lack of any parameter guidance reduces it to 3.

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 ('Delete') and the resource ('a tag'), making the purpose immediately understandable. It distinguishes itself from siblings like 'update_tag' or 'get_tag' by specifying deletion. However, it doesn't explicitly mention what happens to associated data (e.g., if tag is removed from workflows), which prevents a perfect score.

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 guidance by stating 'Requires write_mode', which implies a prerequisite permission context. However, it doesn't explicitly say when to use this tool versus alternatives like 'update_tag' for modification or clarify if deletion is irreversible. No specific exclusions or comparisons to siblings are provided.

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