openstack_list_volumes

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

With no annotations, the description must carry the burden of behavioral disclosure. It simply says 'List block storage volumes' without explaining the role of the required device_id, whether it lists all volumes or filters by device, or any other behavior like pagination or read-only nature.

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 concise sentence that states the purpose without any waste. It is well-structured and front-loaded with the action and resource.

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?

While the core purpose is clear, the description is incomplete given the required device_id parameter and no output schema. The ambiguity of how device_id relates to listing volumes leaves a significant gap, especially with many sibling list tools that might have different scopes.

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 100%, so the baseline is 3 even though the description adds nothing about parameters. The schema description 'OpenStack device ID' is vague, but the description doesn't clarify it either, so it does not 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 clearly states the tool lists block storage volumes in OpenStack (Cinder), using a specific verb and resource. It distinguishes from sibling tools like openstack_list_servers or openstack_list_images by specifying the exact OpenStack service (Cinder).

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 explicit exclusions or alternative tool suggestions. Usage is implied by the clear purpose, but there is no guidance on when to choose this over other list tools, making it only minimally adequate.

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