n8n_update_tag

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

No annotations are provided, so the description carries full burden. It discloses no behavioral traits: no mention of atomicity, whether workflows using this tag are affected, required permissions, or what the operation returns.

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?

Extremely brief (four words), but front-loaded with '[UNIFIED]' metadata that consumes space without adding value. No verbosity, but wastes the first word on an unexplained category tag.

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?

Inadequate for a mutation tool with zero annotations and no output schema. Fails to compensate for the 0% schema coverage by explaining the 'site' parameter's purpose or what constitutes a valid 'tag_id'.

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 coverage is 0% (all three parameters undocumented in schema). The description mentions 'tag name' implying the 'name' parameter, but provides no semantic meaning for 'site' (which n8n instance?) or 'tag_id' (UUID vs slug?), leaving two-thirds of parameters 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 the core action ('Update') and resource ('tag name'), which is clear but minimal. It fails to distinguish from siblings like 'n8n_set_workflow_tags' (which assigns tags to workflows) vs updating the tag entity itself, and the '[UNIFIED]' prefix is unexplained noise.

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?

Provides zero guidance on when to use this versus alternatives (e.g., when to update a tag name vs deleting/recreating it), and no mention of prerequisites like needing the tag_id from n8n_list_tags first.

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