n8n: Delete tag

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no note on irreversibility, whether the tag is detached from workflows/entities, or what happens on a nonexistent tag. It does not contradict the annotations, but it contributes no extra behavioral context.

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 sentence is short but under-specified rather than concise; it spends its few words repeating the name and an unexplained bracket tag. There is no front-loaded scope or key constraint because none is provided.

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 tool with two undocumented required parameters and no output schema, the definition is inadequate. An agent cannot determine what "site" means, whether deletion is recoverable, or how to handle missing tags.

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% for both parameters, and the description supplies no meaning for either. In particular, "site" is highly ambiguous (which n8n instance or tenant?) and "tag_id" format is undocumented, so the description fails to compensate for the coverage gap.

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 "[UNIFIED] Delete a tag" simply restates the tool name and title without adding scope or differentiation. It does not clarify which system's tag is deleted or how this differs from siblings such as gitea_delete_tag or wordpress_delete_tag. The only added token, "[UNIFIED]", is unexplained jargon.

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 tool versus alternatives, no prerequisites, and no mention of what must exist beforehand (e.g., the tag must already be created). With two required parameters and many sibling delete tools, the absence of routing guidance is a real gap.

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