n8n: Create tag

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens on duplicate names despite idempotentHint=false, what permissions are required, or what the response contains. The '[UNIFIED]' prefix is unexplained jargon rather than 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?

A single short front-loaded sentence with the verb leading, which is efficient. The '[UNIFIED]' prefix is noise that consumes attention without adding information.

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 mutation tool with two entirely undocumented parameters and no output schema, one sentence is not enough. Missing are the meaning of 'site', duplicate-name behavior, and any indication of what a successful creation returns.

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 both parameters rely entirely on the description, which explains neither. 'name' is at best implied by 'tag', and 'site' — likely which n8n instance to target — is never mentioned, leaving a required selector parameter undocumented.

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?

States a specific verb and resource ('Create a new tag') plus a scope ('for workflow organization'), which distinguishes it from the delete/get/update tag siblings by verb alone. It never names those siblings explicitly, so differentiation is implicit rather than stated.

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 when-to-use guidance, no mention of alternatives such as n8n_update_tag for existing tags, and no prerequisites (e.g., whether a tag name must be unique per site). The agent must infer all routing and preconditions.

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