List volumes

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does communicate the scope ('all Longhorn volumes') and the read-only nature of listing is implied, but it does not mention return format, pagination, or potential side effects. This is minimal but not completely absent.

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 followed by a documentation link. It is front-loaded and efficient, though the docs link points to 'create-volumes' which is arguably off-topic for a list operation, slightly reducing the score.

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?

For a simple zero-parameter list tool, the description is minimally sufficient: it names the resource and action. However, it lacks any mention of the return payload structure or behavioral nuances, which would be helpful given there is no output schema. The documentation link provides some external context.

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, so the schema already fully documents the input space. The description correctly adds no parameter information since there is nothing to explain, matching the baseline of 4 for zero-parameter tools.

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 all Longhorn volumes' with a specific verb ('List') and resource ('Longhorn volumes'), and the qualifier 'all' distinguishes it from single-volume tools like volume_get. It is unambiguous and easily distinguishable from siblings.

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 usage is implied by the straightforward 'List all Longhorn volumes' purpose, but there is no explicit guidance about when to use this versus alternatives like volumeattachment_list or snapshot_list. No exclusions or conditions are provided beyond the basic action.

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