n8n_delete_tag

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

The description adds no behavioral detail beyond the destructiveHint annotation; it simply restates the delete action. It does not mention whether deletion is permanent, affects workflows using the tag, or how errors are handled. It does not contradict the annotations, but provides no additional transparency.

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 a single, direct sentence with no unnecessary wording. It is front-loaded and easy to parse, which is ideal for a simple tool definition.

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 one-parameter delete tool with a clear schema and destructiveHint annotation, the description is nearly complete. It could mention side effects such as whether the tag is removed from workflows or whether deletion is irreversible, but the core information needed to invoke the tool is present.

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?

The input schema fully documents the single parameter 'id' as 'Tag ID to delete', so schema coverage is 100%. The description adds no extra parameter semantics, but none are necessary given the schema's clarity.

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 action ('Delete') and resource ('a tag') explicitly, making the tool's purpose immediately obvious. It also distinguishes the tool from sibling tag operations (create, get, list, update) and from deletion tools for other resource types.

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, nor any mention of prerequisites or conditions that should hold before deletion. The description relies entirely on the verb 'Delete' to imply usage.

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