docker_volume_list

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

The '[SAFE]' tag hints at non-destructiveness but is not an official annotation. No other behavioral traits (e.g., data source, side effects, required permissions) are disclosed. Since annotations are absent, the description fails to compensate.

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 extremely concise with one sentence. It is front-loaded but lacks substance. For a tool with no parameters, the length is acceptable, but more detail would improve completeness.

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 no output schema and absent annotations, the description provides insufficient context. It does not explain the return format, scope of volumes listed, or any prerequisites (e.g., Docker daemon running). A simple list tool still benefits from minimal context.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds no parameter-specific meaning, but none is needed.

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 action ('List') and resource ('Docker volumes'). It distinguishes itself from sibling tools by specifying 'volumes' among other Docker-related tools like docker_container_list and docker_image_list.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use it, or how it differs from other Docker list tools.

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