Get Version

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond those annotations—no mention of error behavior, existence requirements, authentication needs, or how a missing version is handled.

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 six words and front-loaded with the key verb and resource. There is no filler, repetition of the title, or unnecessary detail that would dilute the message.

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 get-by-identifier tool with a fully described input schema, comprehensive annotations, and an output schema present, the description is sufficient. The only minor gap is the lack of a pointer to list_versions for discovering version numbers, but this is not essential for correct invocation when the caller already knows the version.

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 100%, with all three parameters already described clearly (script_id, version_number, user_google_email). The description does not add extra parameter semantics, so the baseline score of 3 is appropriate since the schema carries the burden.

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 operation ('Gets details') and the resource ('a specific version'), which is more specific than a generic 'get version'. It does not explicitly differentiate itself from sibling tools like list_versions or create_version, but the phrase 'specific version' implies a single-object retrieval rather than enumeration or creation.

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 intended use is implied: retrieve details for one known version using its version_number. However, the description provides no explicit when-to-use guidance, no exclusions, and does not mention that list_versions should be used when version numbers need to be enumerated or when all versions are needed.

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