list_volumes

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

readOnlyHint=true already tells the agent this is a non-destructive read, so the '[READ]' tag is largely redundant. The description does add one piece of value beyond annotations by naming the returned fields (name, driver, mountpoint, scope), but it says nothing about ordering, filtering behavior, or result size.

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?

Two compact lines with the purpose front-loaded and the return fields and argument explained without filler. The bracket tag is slightly redundant against the annotations, which is the only minor waste.

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?

With no output schema, naming the returned fields is exactly the right compensation, and the single argument is fully explained. For a simple read-only listing the definition is essentially complete, though it omits any hint about ordering or pagination of results.

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%, so the description must carry the parameter semantics, and it does: 'target' is documented as a 'Target name from config' with 'omit for the default.' That explains both the value source and the defaulting behavior that the bare anyOf/null schema does not.

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?

States a specific verb and resource ('List named volumes') and enumerates the returned attributes, which distinguishes it from inspect_volume and dangling_volumes by implication. The scoping word 'named' is the only signal separating it from the dangling-volume sibling, so differentiation is present but implicit rather than explicit.

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?

There is no statement of when to use this tool versus dangling_volumes, inspect_volume, or list_images, and no prerequisites or exclusions are given. The '[READ]' marker implies a safe read but does not route the agent among the many sibling listing tools.

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