list-prompt-versions

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

No annotations provided, so description bears full burden. It mentions pagination and return format but does not disclose read-only nature, authentication needs, or side effects. Minimal extra value beyond tool name.

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 fairly concise with three sentences plus an example. It front-loads the core action but includes example and expected return, which add value without excess.

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 list tool with two parameters and no output schema, the description provides purpose, example, and return format. However, it lacks explicit parameter descriptions, pagination details (e.g., cursor), and authentication context. Adequate but with gaps.

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%, so description should explain parameters. It only indirectly hints at 'prompt_identifier' via example and does not describe 'limit' or its default/maximum. Adds little meaning beyond schema.

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 it lists versions for a specific prompt, with a verb ('Get a list of') and resource ('versions for a specific prompt'). It is clear but does not differentiate from siblings like 'get-prompt-version' or 'list-prompt-version-tags'.

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 provides an example usage and expected return, implying when to use, but does not explicitly state when to use this tool over alternatives like 'get-prompt-version' or context for exclusion.

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