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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only that it returns 'headers' (i.e., metadata rather than full version bodies), which is modest context; it says nothing about pagination, result limits, or ordering of the version history.

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 core sentence is short and front-loaded, with the purpose stated immediately. The trailing 'Tools revision: 5c9bea8f.' is internal build noise that consumes space without helping tool selection.

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?

An output schema exists, so return-value details are unnecessary, and annotations fully carry the safety profile. However, for a single-parameter tool with zero schema coverage, the definition leaves the container identifier format and the discovery/usage path unexplained, which is a meaningful gap for correct invocation.

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 sole required parameter 'container' has 0% schema description coverage, yet the description never explains what value to supply (container ID, path, or name) or how to obtain it from gtm_list_containers. With the schema silent, the description should compensate but does not.

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 (container's published/version history headers), which separates it from gtm_list_containers and gtm_list_workspaces by naming the version-history dimension. It's clear what it does, though it doesn't explicitly contrast with the sibling container-listing tools.

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 / when-not-to-use guidance, no mention of prerequisites (e.g., needing a container identifier first), and no named alternatives among the dozens of gtm_* siblings. The agent must infer usage from the noun phrase alone.

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