gtm_delete_variable

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does add one key behavioral detail: the deletion only proceeds when confirm=true is passed. However, it does not explicitly state the irreversible nature of deletion, potential cascading effects, or any required permissions, leaving significant gaps.

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 exceptionally concise, using two short sentences that deliver the core action and the critical confirmation requirement with no filler. Every word earns its place, and the key information is front-loaded.

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?

Given the absence of annotations and output schema, the description is too sparse to be contextually complete. It does not explain the outcome of deletion, whether it is reversible, potential errors, or any side effects. The confirm requirement is helpful but insufficient for a destructive operation.

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?

The description adds meaningful semantics for the confirm parameter by specifying it must be true, which is not evident from the schema's default of false. However, with 0% schema coverage, it fails to provide any guidance on the four ID parameters, though these are fairly self-explanatory from their names.

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 clearly states the action 'Delete' and the target 'variable', making the tool's purpose unambiguous. While it doesn't explicitly name alternative tools, the resource type in the description and tool name inherently distinguish it from sibling delete tools such as gtm_delete_tag and gtm_delete_trigger.

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 or any prerequisites beyond the confirm requirement. The phrase 'Requires confirm=true' is a usage constraint, not a contextual guideline. No mention of exclusions or scenarios is made.

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