list_volumes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all volumes' implies a read-only operation, but it doesn't specify whether it requires permissions, returns paginated results, includes metadata, or has rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 'List all volumes' is extremely concise—three words that directly convey the core action. It's front-loaded with the verb and resource, with no wasted words or unnecessary elaboration. This efficiency makes it easy to parse and understand at a glance.

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's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what 'volumes' are in this context or what the output might look like (e.g., a list of volume objects). For a basic list operation, it meets the bare minimum but could benefit from slight elaboration to enhance usability.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for 0 parameters, as the schema fully covers the absence of inputs, and the description doesn't need to compensate.

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 'List all volumes' clearly states the verb ('List') and resource ('volumes'), making the basic purpose understandable. However, it lacks specificity about what 'volumes' refers to (e.g., storage volumes in a cloud context) and doesn't differentiate from siblings like 'list_servers' or 'list_networks', which follow a similar pattern. It avoids tautology but remains somewhat vague without contextual elaboration.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication state), exclusions (e.g., filtered volumes), or related tools like 'create_volume' or 'delete_volume' from the sibling list. Without such context, an agent might struggle to apply it appropriately in complex scenarios.

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