docker_volumes

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

No annotations are present, so the description bears full responsibility for disclosing behavioral traits. It merely states 'List Docker volumes' without mentioning scope (e.g., all volumes vs. used volumes), side effects (none expected), or any prerequisites. This is a critical gap.

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 sentence with no wasted words. However, it could be slightly more informative (e.g., noting that it lists all volumes) without sacrificing conciseness. Still, it is very efficient.

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 has no parameters and an output schema exists (reducing the need to describe return values), the description is minimally complete. However, it lacks behavioral context and does not clarify what 'volumes' means (e.g., named volumes only, or all volumes). This is adequate but not thorough.

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 tool has zero parameters, and schema description coverage is trivially 100%. With no parameters, the description adds no further meaning, but the baseline score of 4 is appropriate because the schema already fully documents the input. The description is adequate.

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 Docker volumes." uses a specific verb ('List') and resource ('Docker volumes'), clearly distinguishing it from sibling tools like docker_ps, docker_images, and docker_networks which list other Docker resources.

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. With many sibling Docker listing tools, the description should at least imply when to choose volumes over containers or images, but it does not.

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