Delete a tag

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

Annotations already cover the safety profile (destructiveHint=true, idempotentHint=false, readOnlyHint=false), so the bar is lower, and the description clears it by disclosing the real-world side effect: links survive but lose their tag association. It stops short of stating whether the deletion is permanent/reversible or that the `confirm` flag must be true, which would have made it a 5.

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 tight sentences with the core action front-loaded and the consequence following. Every sentence earns its place and there is no filler.

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 mutation with no output schema, the description tells the agent what happens to dependent links, which is the key unknown. It does not address reversibility, error cases, or the confirm requirement, but annotations plus the 100%-covered schema fill most of the remaining gaps.

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 all three parameters (id, account, confirm) are documented in the schema, so the baseline is 3. The description adds no additional meaning about which ID is expected or how the workspace profile and confirm flag interact with the deletion.

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 ("Delete a tag from the workspace"), which is clearly distinct from the other delete_* siblings (delete_link, delete_domain, delete_folder) by resource name. The description itself does not explicitly call out that distinction, so it lands just shy 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?

No indication of when to use this tool versus update_tag, delete_folder, or removing tags from individual links. It also omits any prerequisite or workflow context (e.g., confirming before destructive removal), leaving the agent to infer usage entirely.

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