gtm_version

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

No annotations are provided, so the description carries full burden. It mentions pagination limits (20 items per page) but fails to disclose whether operations are destructive, require authentication, or have other side effects. For a tool with multiple mutation actions, this is a significant 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?

The description is two sentences: the first lists operations, the second provides pagination advice. It is front-loaded with the purpose and contains no fluff. Every sentence earns its place.

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?

Despite 10 parameters and no output schema, the description does not explain required parameters (accountId, containerId), what the tool returns, or prerequisites for each action. Pagination advice is useful but insufficient for a complex tool handling multiple operations.

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 100%, so baseline is 3. The description adds value by explaining that pagination parameters (page, itemsPerPage) are only used when resourceType is specified, and that resourceType helps avoid response truncation. This enhances the schema descriptions.

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 verb ('performs') and the resource ('container version operations'), and lists all seven specific operations. This distinguishes it from sibling tools like gtm_tag or gtm_trigger which handle 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?

The description provides explicit guidance on when to use pagination: for 'get' and 'live' actions with 'resourceType'. However, it does not specify when not to use the tool or offer alternatives for other operations.

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