get_gtm_version

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds significant behavioral context: it returns metadata and entity counts, includes lists of names, and takes a snapshot at a point in time. These details go beyond the annotations, helping the agent understand the tool's behavior and output.

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 three sentences, each earning its place: first states purpose, second lists return components, third gives usage guidance. It is front-loaded, concise, and contains no fluff, making it easy for the agent to parse quickly.

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?

Given the presence of an output schema, the description appropriately focuses on usage and return highlights. However, it fails to explain the optional parameters, which is a gap for a tool with only 3 parameters. Otherwise, it is complete for a read-only retrieval tool.

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%, meaning the schema provides no parameter descriptions. The description does not explain the parameters beyond implying container_version_id is the key. It omits any explanation of gtm_account_id and gtm_container_id, which are optional. This lack of semantic detail forces the agent to infer, which is insufficient.

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 retrieves full metadata and entity counts for a single GTM container version, specifying the returned fields (name, description, fingerprint, lists of tag/trigger/variable names). It effectively distinguishes from sibling tools like list_gtm_versions, which likely only list versions without full details.

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?

Explicitly provides a usage scenario: 'Use after list_gtm_versions when correlating a metric drop with a specific publish.' This tells when to use it and in what context, offering clear guidance beyond a generic description.

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