volume_list

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

Discloses that it returns 'a list of volume attrs dicts' and explains managed_only behavior. Annotations already confirm read-only, non-destructive nature; description adds useful return type info.

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?

Concise with clear args section; front-loaded purpose. Could improve structure with more formatting but no wasted sentences.

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?

Sufficiently complete for a listing tool: explains return type and both parameters. No output schema, but description covers key aspects. Minor gaps in filters format details.

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 0% schema coverage, description compensates by explaining 'filters' (e.g., dangling, name, label) and 'managed_only' (MCP server label filtering). Adds meaning beyond bare schema.

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?

Clearly states 'List volumes' with specific verb and resource. Differentiates from siblings like volume_create, volume_inspect, volume_prune, volume_remove which have distinct purposes.

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?

Provides context for managed_only filter (listing volumes created by this server) but does not explicitly state when to use alternatives like volume_inspect for single volume details.

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