templates_delete

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

No annotations are provided, so the description must convey behavioral traits. It discloses the destructive nature via '[DELETE]' and the requirement for confirmation and an environment variable, which indicates safety guards. This adds value beyond the raw schema.

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 a single, efficient sentence. It front-loads the action and prerequisites with no unnecessary words. Every element serves a purpose.

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 simple delete operation with 5 parameters and no output schema, the description covers the core behavior and guards. It doesn't mention return values or error scenarios, but given the tool's simplicity, it is sufficiently complete.

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 input schema has 100% coverage with individual parameter descriptions, but the description adds context that the confirm parameter is mandatory and ties it to a global environment flag. This helps the agent understand the parameter's importance beyond its type.

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 a GTM template') with a specific verb and resource. It distinguishes from sibling delete tools (e.g., tags_delete, triggers_delete) by specifying 'GTM template'. The [DELETE] prefix is redundant but not misleading.

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 explicit prerequisites: requires GTM_MCP_ENABLE_DELETES=true and confirm=true. This guides the agent on conditions for safe usage. However, it does not explicitly contrast with alternatives (e.g., when to use revert instead), but the name and resource type imply the context.

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