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

The description explicitly states the deletion is permanent and irreversible, which fully discloses the destructive nature of the operation. This aligns with the destructiveHint annotation and provides clear expectations to the agent.

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 succinct, with no unnecessary words. It conveys all essential information in two sentences, making it easy to parse and understand quickly.

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?

The description covers the key aspects: what happens (permanent deletion), the scope (everywhere applied), and the safety precaution (confirm with user). It does not mention return values or additional side effects, but for a simple delete operation, this is sufficient. A minor gap is that it doesn't specify what happens if the tag does not exist, but that is not critical.

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 only parameter 'id' is minimally described in the JSON schema (type string) without additional context in the description. Since the schema already covers the existence and type of the parameter, the description adds no extra semantic meaning, so a baseline score of 3 is appropriate.

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 (delete), the resource (tag), and the scope (removed everywhere it is applied). It distinguishes itself from sibling tools like create_tag and update_tag without needing to reference them.

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?

It explicitly advises confirming with the user before deleting, which is a critical usage guideline for destructive operations. This tells the agent when and how to invoke the tool safely.

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