triggers_delete

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

With no annotations provided, the description carries the full burden. It discloses the destructive nature via [DELETE] and the confirm flag requirement. However, it omits details about potential side effects (e.g., impact on tags using the trigger) or the response format.

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, front-loaded sentence that efficiently conveys action, resource, and requirements with 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 simple delete tool, the description covers the core action and prerequisites, but lacks explanation of parameter semantics and return values. Given the low schema coverage and no output schema, completeness is adequate but not thorough.

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 schema has 0% description coverage for 5 parameters. The description only adds meaning for 'confirm' (must be true) and the environment variable. The IDs (accountId, containerId, etc.) are left unexplained, leaving the agent to infer their purpose 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?

The description clearly states the action ('Delete') and the resource ('a GTM trigger'), with the HTTP method [DELETE] for clarity. It effectively distinguishes from sibling tools like triggers_list or triggers_update.

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 explicitly mentions prerequisites: environment variable GTM_MCP_ENABLE_DELETES=true and confirm=true. This tells the agent when the tool is usable, though it does not explicitly state when to avoid it or list alternatives like disabling the trigger.

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