Gtm.List Triggers

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing but says nothing about pagination, result ordering, empty-result behavior, or what happens with an invalid workspace path.

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?

A single front-loaded sentence with no filler. It is efficient, though the terseness borders on under-specification rather than optimal economy.

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 tool with no annotations, 0% schema description coverage, and a required identifier parameter, the description supplies neither the path format nor any behavioral or usage context. The output schema covers return values, but that is the only dimension not left to guesswork.

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 0% for the single required parameter, so the description must compensate. 'Under a workspace path' hints that workspace_path is a hierarchical GTM path, but gives no format example (accounts/{a}/containers/{c}/workspaces/{w}) or validation expectations.

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?

States a specific verb (List) and resource (triggers) scoped to a workspace path, which distinguishes it from gtm.list_tags, gtm.list_variables and gtm.list_versions by resource name alone. It does not, however, say how it relates to gtm.list_workspaces or what a 'workspace path' is.

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?

There is no when-to-use guidance, no exclusion, and no mention that workspace_path must first be obtained from gtm.list_workspaces. The agent must infer the call chain from the sibling names.

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