delete_tag

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

With no annotations, the description carries the full behavioral burden. It says nothing about irreversibility, whether the delete is permanent or trashable, permission requirements, or what happens to tasks already tagged with it. 'Web mode only' is the sole behavioral detail offered.

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 terse sentences, front-loaded with the action and followed by the environment constraint. No waste, though it is so short that brevity shades into under-specification for a destructive operation.

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, annotation-less tool with no output schema, the description is too thin: it omits reversibility, side effects on tagged items, and permission needs. The schema covers the input, but the behavioral envelope an agent needs before deleting data is absent.

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 coverage is 100% and the single 'name' parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no value about the name parameter (e.g., exact-match vs case-insensitive lookup), but nothing is missing from structured data.

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 and distinct from siblings like rename_tag, merge_tags, and list_tags. It lacks any sibling-differentiating conditional (e.g., when to delete vs merge), so it falls short of a 5.

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?

'Web mode only' is a real usage constraint that tells the agent this tool is unavailable in other modes, which is more than nothing. However, it gives no guidance on when deletion is the correct action versus merge_tags or rename_tag, and no preconditions or warnings.

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