n8n_delete_tag

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies destruction, the description fails to state whether deletion is permanent, irreversible, or what happens if the tag_id doesn't exist. For a destructive operation, this lack of warning is a significant gap.

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 brief (one sentence), but the '[UNIFIED]' prefix appears to be metadata noise that doesn't help the agent understand the tool's function. Every sentence should earn its place; the bracketed text wastes tokens without adding value.

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?

Given the 0% schema coverage, lack of annotations, and absence of an output schema, the description is insufficient. It fails to explain the two parameters, distinguish from similar tools, or describe behavioral consequences, leaving critical gaps in the agent's understanding.

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%, meaning neither 'site' nor 'tag_id' are documented in the schema. The description does not compensate by explaining what 'site' refers to (instance identifier?), the format of 'tag_id', or where to obtain these values. It adds no semantic value beyond the parameter names themselves.

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 basic action ('Delete a tag') but includes noise ('[UNIFIED]') and fails to distinguish from the sibling tool 'n8n_delete_tags' (plural), which likely performs bulk deletion. Without this differentiation, the agent cannot select the correct tool for single vs. multiple tag deletion.

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?

No guidance provided on when to use this tool versus alternatives (e.g., 'n8n_delete_tags' for bulk operations), nor any prerequisites or warnings about the deletion being permanent. The agent receives no decision-making context.

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