versions_create

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

With no annotations, the description carries full burden. It discloses it is a write operation, requires confirm=true, and does not publish. It could elaborate on state changes (e.g., no destructive overwrite) but is adequately transparent.

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 '[WRITE]' and purpose. Every sentence adds value with no redundancy.

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 core purpose and a key prerequisite, but lacks explanation of many parameters and does not describe return value. Incomplete for a 6-param write tool with no output schema.

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 description coverage is only 33% (name/notes have minimal descriptions). The description does not explain required parameters (accountId, containerId, workspaceId, confirm) beyond mentioning confirm=true. It adds no value over the schema.

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 'Create' and resource 'GTM container version from a workspace (checkpoint)', and distinguishes it from sibling tools like 'workspace_create_version_and_publish' by noting it is a snapshot without publishing.

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 specifies prerequisites (GTM_MCP_ENABLE_WRITES=true and confirm=true) and explains the action as a snapshot without publishing, providing context for when to use. It does not explicitly name alternatives or when not to use, but the purpose is clear enough.

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