list_volumes

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

Uses '[READ]' to indicate read-only operation, and lists output fields. With no annotations provided, the description adequately conveys behavioral traits, though it could mention prerequisites or side effects if any.

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?

Extremely concise: two sentences front-load the read status and purpose, then describe the parameter. No wasted words.

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 simple input (one optional param) and no output schema, the description provides sufficient detail to understand purpose and return values. Could potentially mention if there is any filtering or pagination, but not essential.

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?

Explains the single parameter 'target' with its purpose ('Target name from config') and behavior when omitted ('use the default'). This adds significant value beyond the schema, which has 0% description coverage.

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?

Clearly specifies the verb 'List' and resource 'volumes', and details the fields returned (name, driver, mountpoint, scope). Distinguishes from sibling list tools by targeting volumes specifically.

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?

Describes what the tool does and mentions omitting target for default, but does not provide explicit when-to-use or when-not-to-use guidance relative to sibling tools like list_containers or list_networks.

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