delete_tag

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

Beyond the destructiveHint annotation, the description explains the permanent nature, that the tag is removed from every tagged item, and that items survive. It also discloses the confirmation mechanism, adding valuable behavioral context beyond the annotation.

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 compact and front-loaded with 'PERMANENTLY delete', immediately conveying severity. Every word adds value, covering side effects and the confirmation requirement in one sentence.

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 simple destructive tool with two parameters, the description covers the action, scope ('removed from every tagged item'), survival of items, and the confirm requirement. No output schema is needed, and the description is sufficient for an agent to invoke correctly.

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?

With 0% schema description coverage, the description compensates by explaining that 'confirm' must equal the tag's exact name, which clarifies its purpose. The 'name' parameter is implicitly the tag's name from context. The description adequately explains the critical confirm parameter, but 'name' is left to inference.

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 clearly states the action 'PERMANENTLY delete a tag itself' with a specific resource (tag). It distinguishes from deleting tagged items by noting 'the items survive', which differentiates it from sibling delete tools like delete_item.

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?

The description implies when to use this tool by clarifying it deletes the tag entity, not the associated items. It also provides a usage requirement (confirm must equal the tag's exact name). However, it does not explicitly name alternative tools or state when not to use it, though the contrast with delete_item is implied.

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