list_volumes

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

There are no annotations provided, so the description carries the full burden. It discloses the ordering behavior ('display order'), but does not explicitly mention read-only nature, permissions, or error behavior. While 'list' implies safety, the description adds only minimal behavioral context beyond the 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 a single sentence that directly conveys the function and a distinguishing detail. No redundant words or unnecessary information.

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?

The tool is simple (one parameter) and an output schema exists, so return values need not be explained. The description is sufficient for understanding what the tool does and the ordering behavior. It could mention edge cases or that it lists all volumes, but these are largely implied by the name and verb.

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%, but the description does not explain the project_id parameter beyond the schema's name and type. It only mentions 'an OpenFic project' without clarifying that project_id is the identifier to use. The description fails to compensate for the lack of schema descriptions, even though there is only one parameter.

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 the tool lists volumes of an OpenFic project, using a specific verb ('List') and resource ('volumes'). It also adds a distinguishing detail ('in display order') that differentiates it from sibling tools like get_volume, which retrieves a single volume.

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 usage is implied: it is used when you need to list all volumes for a given project. However, it provides no explicit comparison to alternatives (e.g., get_volume for a single volume) or exclusions, so it falls short of clear guidance.

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