prompts_get_version

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

With no annotations, the description carries the full burden of behavioral disclosure. The verb 'Get' implies a read-only operation, but nothing is said about error behavior, permissions, rate limits, or what happens when the requested version does not exist. The output schema covers return shape, but not behavioral traits.

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 efficient sentence that front-loads the verb and resource with no filler. It is appropriately concise, though it achieves brevity at the expense of useful context.

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 two-parameter getter with an output schema, the description is minimal but incomplete: it lacks parameter semantics, usage guidance to distinguish from sibling tools, and behavioral context. The output schema mitigates the return-value gap but not the other omissions.

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 the tool description adds no parameter details. The parameter names 'agent_id' and 'version' are somewhat self-explanatory, but the format of 'version' (e.g., semver, ID, label) and the meaning/scope of 'agent_id' are left undefined.

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 uses a clear verb and resource: 'Get a specific system prompt version content for an agent.' The word 'specific' distinguishes it from prompts_get_current (current version) and prompts_list_versions (listing versions), though it does so implicitly rather than by naming alternatives.

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 is provided on when to use this tool versus its siblings. The distinction from prompts_get_current and prompts_list_versions is implied by the name and description but never stated, leaving the agent to infer the appropriate context.

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