volume_list

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context such as 'Volumes are addressed by name only' and explains how managed_only filters on a specific label. It doesn't contradict the annotations and supplements them with details about return format and filter behavior.

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 reasonably concise at ~90 words and well-structured with a brief intro, usage hint, args, and returns sections. Every sentence adds value, but the 'Volumes are addressed by name only' sentence could be seen as slightly tangential; still, it's important context for how to interact with volume entities.

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?

Despite no output schema, the description specifies the return format as a list of volume documents with example fields. It covers parameters, return type, and alternative tools, making it complete for a list operation with two parameters.

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 has 0% parameter descriptions, but the description thoroughly explains both parameters: filters with examples (dangling, name, label) and managed_only with its label-filtering behavior and how it combines with filters. This fully compensates for the lack of schema descriptions.

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 'List volumes' with a specific verb and resource. It distinguishes itself from sibling tools by noting that volume_inspect is for detail and volume_remove/prune are for cleanup, making its purpose clear.

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 explicitly tells when to use this tool vs alternatives: 'feed a Name to volume_inspect for detail or volume_remove / volume_prune to clean up.' It also gives a concrete example of using filters for dangling volumes, providing strong usage guidance.

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