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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds value beyond that by disclosing the flattened conditions return shape ({filter, op, arg0, arg1}) with a worked example, telling the agent exactly what a read will yield and why it is useful.

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?

Front-loads the core purpose, then the extra conditions detail, then the parameter pointer. Mostly tight, though the inline conditions example is dense enough that it slightly taxes readability. Little waste overall.

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 2-parameter read tool with a full output schema and complete safety annotations, the description covers purpose, the key use case, return shape, and how to obtain the identifiers. Only the parameter defaults and any scoping caveat remain unaddressed.

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% and both parameters (container, workspace) are undocumented in the schema. The description partially compensates by pointing to list_gtm_tags as the source of workspace/container identifiers, but never explains the parameters directly or that both default to empty strings, so the gap is only half-filled.

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+resource ('Lists the TRIGGERS in a workspace') and itemizes the returned fields (name, triggerId, type). It clearly distinguishes itself from list_gtm_tags and list_gtm_variables, and the example types ('pageview'/'click'/'customEvent') leave no ambiguity about what a trigger 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?

Gives a concrete use case: read back and verify a URL/click filter after creating it 'without a live Preview'. It also routes the agent to list_gtm_tags for workspace/container values. It stops short of explicitly contrasting with other list_* siblings, but the primary when-to-use is clear.

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