Create Version

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

The description adds important behavioral nuance beyond the annotations: versions are immutable and cannot be modified after creation. This is disclosed clearly and complements the readOnlyHint=false annotation without contradiction.

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 only two sentences, front-loaded with the primary action, and each sentence adds value. No redundant or filler content.

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?

With annotations indicating a non-read-only, non-destructive operation and an output schema present, the description fully conveys the core purpose and key immutable-snapshot constraint. It is sufficient for an agent to select and invoke the tool correctly.

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% with clear descriptions for script_id and user_google_email, so the baseline is 3. The description adds no parameter-specific meaning beyond 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 states a specific action ('Creates a new immutable version') and resource ('script project'), clearly distinguishing it from sibling tools like get_version or list_versions. It also explains what a version is (a snapshot of current script code).

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 makes the use case clear: create an immutable snapshot of current script code. However, it does not explicitly mention alternatives or when not to use it, though the verb 'creates' naturally differentiates from get_version/list_versions.

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