gtm_delete_tag

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful fact that removal applies to a draft rather than the live container, but does not say whether the change is permanent, whether a sync is needed to propagate it, or whether it can be undone.

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 efficient sentence with the action and scope front-loaded and no filler. The 'explicitly selected' wording is slightly ambiguous but does not waste space.

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?

An output schema and rich annotations exist, so return values and safety are covered. However, for a 4-required-param destructive mutation in a draft/sync workflow, the description never mentions the draft-to-live propagation step, which an agent needs to sequence correctly.

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 75% and account/container/workspace already carry descriptions; tagId is undocumented but self-evident. The description reinforces that the workspace must be explicitly supplied and that all operations target a draft, but adds no syntax or format detail beyond the schema. Baseline 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 ('Delete a tag') plus a scoping qualifier ('from an explicitly selected workspace draft'). It is clearly distinguishable from gtm_revert_tag and gtm_update_tag. It stops short of naming the sibling alternative, so 4 rather than 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 statement of when to use this versus gtm_revert_tag (which also removes a tag's effect) or when deletion is inappropriate. Usage context is only implied by the phrase 'workspace draft'. No prerequisites or follow-up steps are given.

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