podman_volumes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds no extra behavioral context beyond the basic listing operation. It does not contradict annotations, but it also does not disclose any additional traits such as output format or scope.

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, concise sentence. It is appropriately sized for a simple list operation and contains no unnecessary words or repetition.

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's simplicity, the presence of an output schema, and annotations covering safety, the description is mostly complete. It lacks any mention of the format parameter or scope (e.g., 'all volumes'), but these are not critical for a basic listing tool and are largely covered by the schema and name.

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 schema description coverage is 0%, and the description does not compensate for the 'format' parameter. Although the schema fully documents the parameter with enum values and a default, the description offers no additional meaning, leaving the agent to rely solely on the schema for a parameter that could benefit from contextual explanation (e.g., 'json output for machine parsing').

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 '列出 volumes。' clearly states a specific verb (list) and resource (volumes), distinguishing it from sibling tools that operate on containers, images, pods, or networks. It fully captures the tool's purpose.

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 explicit guidance on when to use this tool versus alternatives. However, the resource name and sibling list imply its use for listing volumes. It lacks contextual cues such as 'use this when you need to see available volumes' or exclusions for other resource types.

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