apps_script_create_version

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds the key behavioral trait 'immutable' and 'snapshot of HEAD', which clarifies that this creates a permanent, non-modifiable version. This adds value beyond annotations by explaining the immutability and source.

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 a single, concise sentence that front-loads the core action and key trait (immutable). No wasted words.

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?

For a simple create operation with 2 parameters and no output schema, the description is mostly adequate. However, with 0% schema coverage, it doesn't explain what the description parameter is for or what the response contains. The immutability trait is useful but the tool could benefit from noting that this is a versioning operation tied to a specific scriptId.

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 0%, so the description must compensate. It mentions 'HEAD' but doesn't explain the scriptId parameter or the optional description parameter. The description adds no meaning beyond the schema's basic property names and types.

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 'Create an immutable version snapshot of HEAD' clearly states the verb (create), resource (version snapshot), and source (HEAD). It distinguishes from siblings like apps_script_list_versions and apps_script_get_version, though it doesn't explicitly name them.

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 implies usage: creating a version snapshot of the current HEAD. It doesn't explicitly state when to use this vs alternatives, but the context of versioning is clear. No exclusions or alternative tool names are provided.

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