get-runbook-version

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states the action without addressing error behavior, authentication needs, rate limits, or response format. While it is a read operation, no additional context is supplied beyond the basic 'Get' verb.

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 of seven words, with no unnecessary filler. Every word contributes to stating the action and resource, making it highly concise and well-structured.

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 operation with two required parameters, the description is minimally adequate but incomplete. It does not clarify what a 'version' refers to, the return value, or how to differentiate among version-related tools. Given the lack of an output schema, more context would be beneficial.

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 50%, with only 'version' having a vague description ('Version identifier') and 'runbook_id' having none. The tool description does not elaborate on parameter meanings, relationships, or expected formats, failing to compensate for the schema's gaps.

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 'Get a specific version of a runbook' clearly states the action (get), the resource (a specific version of a runbook), and distinguishes it from sibling tools like get-runbook (whole runbook) and get-runbook-versions (list all versions). The specificity of 'a specific version' prevents confusion with plural versions.

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 offers no guidance on when to use this tool versus alternatives such as get-runbook (current runbook) or get-runbook-versions (listing versions). It does not mention exclusion criteria or provide context for tool selection.

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