Get Agent Version

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds no additional behavioral context, such as what happens if the version is not found, whether authorization is needed, or what the response contains. With annotations covering the core safety traits, a baseline score of 3 is appropriate.

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 sentence, 'Fetch a specific version of an agent,' with no unnecessary words. Every word contributes to the meaning. It is appropriately concise for a simple retrieval operation.

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 tool with two well-documented parameters and strong annotations (read-only, idempotent, non-destructive), the description is nearly complete. It could mention that the tool returns version data or that the version must belong to the given agent, but the operation is straightforward and the schema covers parameters. The lack of an output schema is compensated by the clarity of the operation.

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?

The input schema has 100% coverage: both agent_id and version_id have descriptions ('The agent_id' and 'The version_id to fetch'). The description adds no extra meaning beyond what the schema provides. Baseline is 3 when schema coverage is high, so no additional credit is warranted.

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 'Fetch a specific version of an agent' clearly states a fetch operation and distinguishes it from sibling tools like lyzr_get_agent (fetch the agent itself) and lyzr_list_agent_versions (list versions). The verb 'fetch' and the noun 'specific version' are precise, though it could be slightly more explicit about returning version data.

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 guidance on when to use this tool versus alternatives. The description does not mention that to list all versions one should use lyzr_list_agent_versions, or that this tool is meant for retrieving a single version by ID. No prerequisites, exclusions, or alternative tool references are provided.

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