delete_tag

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

Annotations already set destructiveHint=true and readOnlyHint=false. Description reinforces the destructive nature with a warning and permission requirement, adding necessary context beyond annotations.

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?

Two sentences plus a warning; each sentence serves a purpose: alerting about destructiveness, describing action, and providing guidance. No redundancy.

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 one-parameter delete tool, the description covers key aspects: destructive action, permission requirement, and ID retrieval method. Output schema exists (not shown) but doesn't need explanation. Slight gap in parameter details.

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?

Only parameter is 'id' with 0% schema coverage. Description mentions 'by ID' but does not clarify format, source, or constraints. Schema coverage is low, and description fails to compensate meaningfully.

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?

Description clearly states 'Remove a single tag by ID,' specifying the action and resource. It distinguishes from sibling tools like 'remove_tags' which handles multiple tags.

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?

Provides explicit guidance to 'Use list_tags to find the tag ID' and warns about destructive action, asking for user permission. Could mention when not to use (e.g., for batch removal use remove_tags).

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