n8n_update_tag

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

Annotations cover key traits (mutable, idempotent, non-destructive), but the description adds valuable context: it discloses that renaming affects all workflows using the tag automatically, which is crucial behavioral information not captured in annotations. No contradictions with annotations exist.

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 front-loaded with the core action in the first sentence, followed by a concise usage guideline. Both sentences are essential—the first defines the purpose, and the second provides context—with no wasted words.

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 moderate complexity (a mutation with two parameters) and rich annotations, the description is mostly complete. However, without an output schema, it could benefit from mentioning the return value or success indicators, though the behavioral context provided partially compensates.

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 100% description coverage, clearly documenting both parameters (id and name). The description does not add further meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 specific action ('Rename an existing tag') and resource ('tag'), distinguishing it from siblings like n8n_create_tag (creates new tags) and n8n_delete_tag (removes tags). It precisely defines the tool's function without ambiguity.

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 clear context for when to use this tool ('to standardize tag naming across workflows'), but it does not explicitly mention when not to use it or name specific alternatives. For example, it doesn't contrast with n8n_update_workflow_tags for bulk updates.

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