portainer_volumes_list

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

No annotations are provided, so the description must convey behavioral traits. It only states 'List', implying a read-only operation, but does not explicitly mention safety, authorization needs, rate limits, or any side effects. The minimal disclosure leaves gaps for an agent.

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: one sentence stating the purpose, followed by a clean bullet-style parameter listing. Every sentence is useful, and the main verb is front-loaded.

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 that an output schema exists, the description does not need to detail return values. It adequately covers the tool's purpose and parameters. However, it could mention that the operation is a list (implying multiple volumes returned) or any ordering/pagination, but this is minor.

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 input schema has 0% description coverage, so the description carries the burden. It clearly defines both parameters: endpoint_id (target endpoint, defaults if omitted) and name_filter (substring filter). This adds meaningful context beyond the schema's bare types.

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 Docker volumes on an endpoint', specifying the action and resource. It distinguishes from siblings like portainer_volume_inspect (inspect specific volume) and portainer_volume_remove (remove volumes).

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 explains the parameters (endpoint_id defaults, name_filter substring), but does not explicitly state when to use this tool versus alternatives like portainer_volume_inspect or when not to use it. It provides basic guidance but lacks explicit when/when-not contexts.

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