delete_taxonomy_tag

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

With no annotations, the description must disclose behavioral traits. It indicates a destructive 'delete' operation but does not explain whether it permanently removes the tag from the taxonomy or only the association, nor does it mention side effects, reversibility, or permissions. This is a significant transparency gap for a mutation tool.

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 sentence with no redundancy. It is front-loaded and clearly communicates the core action without wasting words, achieving maximum conciseness.

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 mutation tool with no annotations or output schema, the description is too sparse. It fails to clarify the exact effect on the tag (global deletion vs. untagging from a taxonomy), and does not address distinctions from closely related siblings. This leaves significant context gaps for an agent assessing side effects and alternatives.

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 schema has 100% parameter descriptions, but they are generic ('ID of the resource') and unhelpful. The tool description adds no parameter-specific meaning; however, the parameter names (taxonomy_id, id) and the tool's purpose loosely imply roles. Per the baseline for high schema coverage, a 3 is appropriate, though the schema descriptions themselves are weak.

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 a specific action ('Delete a tag from a taxonomy') with a clear verb and resource. However, it does not explicitly differentiate from sibling tools like 'delete_tag' or 'remove_tag_taxonomies', leaving some ambiguity about whether it deletes the tag globally or just the association.

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 is provided about when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or comparisons to sibling tools like 'delete_tag' or 'remove_tag_taxonomies', so the agent would have to infer usage context from the name alone.

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