transformations_delete

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

With no annotations provided, the description indicates a destructive operation via the DELETE prefix and the requirement for a confirm parameter. It adds context about the required environment variable but does not disclose side effects, irreversibility, or potential errors, leaving moderate 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?

Description is extremely concise with two sentences, placing the most critical information first (DELETE label and purpose) followed by the prerequisites. 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?

For a delete operation with 5 required parameters and no output schema, the description covers key prerequisites but omits details like success/failure behavior, idempotency, or rate limits. Given typical GTM tool complexity, it meets a basic standard but lacks full 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 coverage is 100%, so baseline is 3. The description adds value beyond schema by specifying the environment variable requirement (GTM_MCP_ENABLE_DELETES), which is not in the schema. This helps the agent understand a necessary precondition.

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 transformation' with a specific verb and resource. Among sibling delete tools (e.g., tags_delete, templates_delete), this tool is uniquely identified as deleting transformations, making it easily distinguishable.

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?

Description explicitly requires 'GTM_MCP_ENABLE_DELETES=true' and 'confirm=true', providing clear prerequisites for use. However, it does not mention when not to use or suggest alternatives, though no alternative delete tool for transformations exists.

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