versions_delete

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

With no annotations, description fully discloses destructive nature (DELETE), required environment variable, mandatory confirm parameter, and limitation on live versions. This provides comprehensive behavioral context.

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 sentences, each critical: first states action and prerequisites, second adds constraint. Front-loaded with key information, no unnecessary words.

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?

Covers core behavior and constraints but lacks parameter descriptions for the three ID fields. Without annotations or output schema, the description is slightly incomplete for an agent to use the tool without additional context.

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 0%, but description only explains 'confirm' parameter. It does not describe accountId, containerId, or containerVersionId, leaving the agent to infer their meaning from context.

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?

Description clearly states 'Delete a GTM container version' with specific verb and resource. It distinguishes from sibling tools like versions_publish and versions_undelete through constraints like 'Cannot delete a currently published version.'

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?

Explicitly states prerequisites (GTM_MCP_ENABLE_DELETES=true, confirm=true) and a key constraint (no live versions). However, it does not explicitly mention alternatives among siblings like versions_undelete.

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