Update n8n Tag

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

The description adds no behavioral context beyond what the annotations already provide. It does not mention what happens if the tag does not exist, error behavior, or that it is idempotent. The phrase 'existing tag' hints at a precondition, but the description is essentially a tautology of the title and offers no new insights.

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 a single purpose sentence and a compact argument list. It is front-loaded and contains no redundant or filler content. Every element serves a clear function.

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?

The tool is simple and has no output schema, but the description lacks details on return values, error conditions, or side effects. The provided information covers the basic operation and arguments, but it is not fully complete for an agent that might need to know what happens on success or failure.

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?

Both parameters are fully described in the input schema (id: 'Tag ID', name: 'New tag name'), and the description repeats the same information without adding extra meaning. Schema coverage is 100%, so the baseline is 3; the description does not enhance understanding beyond the schema.

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 'Rename an existing tag' uses a specific verb (rename) and resource (tag), clearly distinguishing it from sibling tools like n8n_create_tag, n8n_delete_tag, and n8n_list_tags. It also matches the tool title and leaves no ambiguity about what operation is performed.

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 implies the tool is for renaming existing tags, which is a clear context, but it does not explicitly mention when to use it versus alternatives like create or delete. No exclusions or comparisons are provided, so it relies on the reader's inference from the purpose.

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