List Prompts

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

With no annotations, the description carries the full burden. It communicates that the tool returns prompt content and versions and implies a read-only list operation, but it does not disclose ordering, pagination, or whether all versions are returned for each prompt.

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?

A single, information-dense sentence with no wasted words. The primary action (List all) is front-loaded, and content/versions are specified as the result payload.

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 zero-parameter list tool, the description specifies scope and returned data sufficiently for an agent to select and call it. It could add detail about response shape or limits, but the tool is simple enough that this is not a critical gap.

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 is empty, so there are no parameters to document. The 100% schema coverage baseline for zero-parameter tools applies, and the description introduces no param-related ambiguity.

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 states a specific action (List), the target resource (all available prompts), and the included payload (content and versions). Its all-encompassing scope clearly distinguishes it from the single-item getPrompt and mutating setPrompt siblings.

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 intended use for enumeration is implied by 'List all available prompts', but the description provides no explicit when-to-use guidance or references to alternative tools. An agent can infer the distinction from sibling names, but the description itself doesn't state it.

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