Tag Manager inventory

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond that: it reads only the default workspace, translates built-in trigger ids (e.g. All Pages), and includes the published version id. It does not mention response size or paging, which is the only notable gap.

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?

Two sentences, front-loaded with what the tool returns and no filler. The second sentence is a small add-on hint rather than noise, though the first sentence is slightly dense with parenthetical field lists.

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?

With no output schema, the description does the work of describing the returned data (tags/triggers/variables fields, published version id, translated trigger ids), which is adequate for a zero-argument read tool. It stops short of covering response size, workspace selection assumptions, or error conditions.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies.

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?

Names the exact resource and scope: tags (with type, paused state, firing triggers, parameters), triggers, variables of the container's default workspace, plus the live published version id. That is specific enough to distinguish it from the GA4/GSC/Merchant siblings, which cover entirely different resources.

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?

"Useful to spot a tag configured twice" implies a use case (auditing/duplicate detection) but gives no explicit when-to-use conditions, prerequisites, or alternatives. Usage is inferable rather than stated.

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