n8n: Update tag

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is supplied structurally. The description adds nothing further — it does not say renames overwrite the previous name irreversibly, whether site/tag_id must resolve to an existing tag, or what happens on a name collision.

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?

One short sentence with no padding, so it is efficient, but the bracketed "[UNIFIED]" token consumes space without conveying actionable meaning. The brevity here reads as under-specification rather than tight writing.

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?

For a destructive, non-idempotent mutation with three required undocumented parameters and no output schema, the description is far too thin. An agent cannot determine what a successful rename returns or how to identify the target tag reliably.

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 carries the full burden for all three parameters. It only echoes "name"; the meaning and format of "site" and "tag_id" (identifier type, cross-provider addressing) are left entirely unexplained.

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 states a verb and resource ("Update tag name") and identifies the field being changed, which puts it above a bare restatement of the title. However, the "[UNIFIED]" prefix is opaque and nothing distinguishes this from siblings such as n8n_create_tag, n8n_delete_tag, or wordpress_update_tag.

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?

There is no guidance on when to use this versus the create/delete/get tag siblings, and no mention of prerequisites such as needing an existing tag_id. An agent must infer the workflow from the sibling list alone.

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