delete_tag

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

With no annotations supplied, the description carries the full behavioral burden, yet it omits the crucial facts for a delete operation: whether removal is permanent or reversible, whether it requires confirmation, and whether tasks carrying the tag are affected. 'Deletes' only implies mutation without disclosing any of the consequences.

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?

A single short sentence that is front-loaded and free of filler. It is efficient but borders on under-specification rather than true 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 destructive, unannotated tool with one required parameter and no output schema, the description should at least state permanence and side effects. As written, an agent cannot tell what happens to tasks using the tag or whether the action can be undone.

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?

Schema description coverage is 100% and there is only one parameter ('name', documented as 'Tag name'), so the schema fully covers the input. The description adds no format or identity detail (e.g., ID vs. name matching) beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource (deletes a tag), which is unambiguous on its own. However, it does nothing to distinguish itself from siblings like rename_tag, merge_tags, or list_tags, which all operate on the same resource.

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 delete a tag versus the closely related alternatives, notably merge_tags, which is often the safer choice when a tag is still in use. No prerequisites or warnings about the destructive nature are provided.

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