Tag Manager version details

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

Annotations already indicate readOnlyHint and destructiveHint, and the description adds context by specifying the returned data (name, description, fingerprint, entity lists). No contradiction with annotations.

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 concise sentences, no fluff, with the primary purpose stated upfront and the use case appended. Efficient and well-structured.

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?

Covers purpose, use case, and returned data. Does not explicitly describe prerequisite steps beyond 'after list_gtm_versions', but is sufficient for an agent to decide when to call it. No mention of error conditions, but that is not critical for a simple get.

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 has zero descriptions for parameters, and the tool description does not explain the roles of gtm_account_id, gtm_container_id, or container_version_id. It only implies the version ID comes from list_gtm_versions, leaving the other two parameters ambiguous.

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?

Clearly states the action ('Get'), the resource ('full metadata + entity counts for a single GTM container version'), and distinguishes it from siblings by specifying the use case ('Use after list_gtm_versions').

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?

Provides explicit guidance on when to use the tool ('Use after list_gtm_versions when correlating a metric drop with a specific publish'), which differentiates it from listing or other get operations.

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