Delete a tag

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which covers the safety profile. The description itself adds no behavioral context beyond the bare statement 'Removes a tag.' It does not contradict annotations, but also does not enrich them with additional details like irreversibility or potential side effects.

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 extremely concise with one short sentence that front-loads the core purpose. There is no redundant wording, but it is arguably under-specified rather than appropriately concise, missing opportunities to add usage context. Still, it is well-structured for a simple deletion tool.

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 tool is low complexity, with a clear schema and annotations covering destructive behavior. However, the description alone does not fully convey the need for confirmation or any consequences. Given that the schema and annotations fill in many gaps, the description is minimally viable but not comprehensive.

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%, so the baseline is 3. The description itself adds no parameter-specific information, but the schema already explains tag_id, confirm, and workspace_id. The confirm parameter's const true is a safety mechanism that the description does not elaborate on, but the schema covers it.

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 'Removes a tag' uses a specific verb and resource, clearly distinguishing it from sibling tools like clockify_create_tag and clockify_update_tag. It is unambiguous about the action performed.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that deletion is permanent, that confirmation is required, or when one might prefer updating instead. No contextual or exclusionary information is given.

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