Get Script Version

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description earns credit for adding the word 'immutable', which signals that versions cannot be altered, but it says nothing about pagination, response shape, or how action changes behavior.

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?

One short sentence with no filler and the resource front-loaded. It is on the terse side for a four-parameter tool, but nothing in it is wasted.

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 0% schema coverage, a required free-form action parameter, and no output explanation needed (an output schema exists), the description is the only source of guidance on how to drive this tool — and it omits both action values and the conditional role of version_number. Inadequate for the tool's actual call surface.

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% and all four parameters are undocumented in the schema. The description gestures at an action concept ('list or retrieve') but never enumerates valid action values, and never explains that version_number is only meaningful for the retrieve case while script_id and user_google_email are always required.

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 names a specific verb pair (list/retrieve) and resource (immutable version snapshots of a script project), which is materially clearer than the bare tool name. However, it does not distinguish this read tool from the sibling manage_script_version, nor does it explain how 'list' vs 'retrieve' map to the required action parameter.

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 statement of when to use this tool versus manage_script_version, get_script_project, or list_script_deployments, all of which sit adjacent in the toolset. The reader is left to infer that this is the read-only counterpart of manage_script_version.

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