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 of behavioral disclosure. It mentions 'Requires write_mode,' which hints at permission needs, but doesn't describe what happens during renaming (e.g., if old tag references are updated, if it's reversible, rate limits, or error conditions). For a mutation tool with zero annotation coverage, 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: 'Rename a tag. Requires write_mode.' Every word earns its place, and it's front-loaded with the core action. There's no wasted verbiage, making it highly efficient in communication.

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 there's an output schema (which should cover return values), the description doesn't need to explain outputs. However, as a mutation tool with no annotations, 0% schema coverage for inputs, and minimal behavioral context, it's only partially complete. It covers the basic action and a prerequisite but misses details on parameters, side effects, and usage nuances.

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%, meaning the input schema provides no descriptions for parameters. The description doesn't add any semantic information about 'tag_id' (e.g., format, source) or 'name' (e.g., constraints, uniqueness), failing to compensate for the lack of schema documentation. With two undocumented parameters, this is inadequate.

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 ('Rename') and resource ('a tag'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'update_workflow_tags' or 'update_execution_tags' which also modify tags in different contexts, so it doesn't reach the highest level of sibling differentiation.

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 'create_tag' or 'delete_tag,' nor does it provide exclusions or detailed contextual guidance beyond the basic requirement.

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