List GTM Triggers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds the returned fields, which is useful. However, it does not disclose pagination behavior despite the page_token parameter, and the claim of 'all triggers' could conflict with paginated results. The description adds some context but not rich behavioral detail.

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, concise sentence with no fluff or redundancy. It efficiently conveys the tool's purpose and output contents.

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 list operation with annotations and full schema coverage, the description is mostly complete. It specifies the output fields but omits mention of pagination, which is relevant given the page_token parameter. Minor gap, but overall adequate.

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 description coverage is 100%, so all parameters are documented in the schema. The description says it lists triggers in a workspace, which reinforces the role of account_id, container_id, and workspace_id, but adds no new semantic detail beyond what the schema already provides. Baseline of 3 is appropriate given full schema coverage.

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 a workspace with specific output fields (IDs, names, types, filter conditions). This distinguishes it from siblings like gtm_get_trigger (single trigger) and gtm_list_tags (different entity).

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 implicitly indicates it is for listing triggers in a workspace, which is clear context. However, it does not explicitly mention when not to use it or name alternatives like gtm_get_trigger for specific triggers. The context is enough for a straightforward list operation.

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