get-model-version

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

Annotations (readOnlyHint=true) already indicate safe read-only behavior. The description adds no additional behavioral context such as error handling, required permissions, or side effects. While not contradictory, it misses opportunities to explain behavior beyond the annotation.

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?

Single sentence with no unnecessary words. Front-loads the action and resource. Efficient and direct.

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?

Despite being a simple retrieval tool with 2 parameters and no output schema, the description omits what is returned (e.g., a model version object), which is critical for an agent. With many sibling tools, more context about the scope or return value would help.

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 covers only 50% of parameters with descriptions (version has a brief example). The description repeats parameter names but offers no additional meaning for 'name' (e.g., that it refers to a registered model name) or further clarification for 'version'. It fails to compensate for the schema's lack of parameter documentation.

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?

Description 'Get a model version by name and version' clearly states the action (get) and resource (model version) with specific identifiers (name and version). It distinguishes from sibling tools like 'get-model-version-by-alias' and 'get-latest-model-versions' which use different identification methods.

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?

No guidance on when to use this tool versus alternatives. With many sibling tools for model versions (create, delete, search, etc.), the description provides no context on when to choose this retrieval method over others, nor any prerequisites or exclusions.

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