list-prompt-versions

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

With no annotations, the description must fully disclose behavior. It mentions 'pagination support' but does not explain the pagination mechanism (e.g., cursor or offset). It also omits error handling (e.g., prompt not found) and ordering details. The expected return is described vaguely as 'Array of prompt version objects with IDs and configuration'.

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 concise with three sentences plus an example. It is front-loaded with the primary action. However, it could be more structured by separating usage from return format.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description is insufficient. It lacks details on pagination behavior, error conditions, and parameter formats, leaving significant gaps for the agent to understand correct invocation.

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 the description must compensate. It only references 'prompt identifier' via example, not its format (name or ID). The 'limit' parameter is mentioned only in schema, and the description adds no explanation of how pagination works.

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 'Get a list of all versions for a specific prompt' which identifies the action (get list) and the resource (prompt versions). It distinguishes from siblings like 'get-prompt-version' (singular) and 'list-prompts' (prompts, not 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 provides an example usage but lacks explicit guidance on when to use this tool versus alternatives (e.g., get-prompt-version). No 'when-not-to' or conditions for use are given.

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