triggers_delete

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

With no annotations provided, the description must carry full burden. It only mentions the requirement for confirm and env var, but does not disclose any behavioral traits such as irreversibility, permissions needed, or error conditions. For a destructive action, this is insufficient.

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 communicates the action and requirements. While concise, it omits important details; however, it does not waste 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?

Given 5 required parameters, no output schema, and a destructive operation, the description is incomplete. It fails to specify what happens after deletion, return values, or parameter formats. For a delete tool, more context is expected to ensure safe usage.

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 0% (no descriptions in schema), and the description does not explain any parameters beyond mentioning 'confirm=true'. The meaning of accountId, containerId, workspaceId, triggerId, and confirm are not clarified, leaving the agent uninformed.

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 'Delete a GTM trigger' with a specific verb ('Delete') and resource ('GTM trigger'). It is unambiguous and distinguishes from sibling tools like triggers_create, triggers_update, triggers_get, etc.

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 lists prerequisites: requires GTM_MCP_ENABLE_DELETES=true and confirm=true. This provides clear when-to-use guidance. However, it does not explicitly state when not to use or mention alternatives, leaving some gap.

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