List Tag Manager triggers

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

The annotations already indicate readOnlyHint=true and destructiveHint=false. The description is consistent with these annotations and does not introduce any contradictory behavior. It adds little beyond the annotations but is transparent about being a listing operation.

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 concise and well-structured, providing a single purpose statement along with an illustrative example. It avoids unnecessary fluff and directly conveys the tool's functionality.

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?

The description provides sufficient context for a simple listing tool. Since an output schema exists, detailing return values is not required. However, it does not mention that all parameters are optional, which might be inferred from the schema but could be stated. Overall, it covers the core aspects adequately.

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 no descriptions for gtm_account_id and gtm_container_id, and the tool description does not explain what these parameters represent or their expected format. While the names are somewhat self-explanatory, the lack of explicit guidance leaves ambiguity for the agent.

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 tool lists all triggers in the live GTM container, provides an example of filter parsing, and indicates its use for diagnosing tag firing. It distinguishes itself from other GTM tools like list_gtm_tags or get_gtm_trigger.

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 gives a clear use case (diagnose why a tag fires or doesn't fire) and implies when to use this tool (when needing to see all triggers). It does not explicitly contrast with alternative tools like get_gtm_trigger, but the usage context is clear enough.

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