List backup volumes

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

No annotations are provided, so the description carries the behavioral transparency burden. It establishes that this is a read-only enumeration of backup-target-side volume records, but it does not mention prerequisites like a configured backup target, pagination behavior, or whether metadata is returned. The docs link helps but the description itself is thin.

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?

A single concise sentence front-loads the action and resource scope, followed by a useful documentation link. There is no filler, redundancy, or unnecessary detail.

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 zero-parameter, read-only list operation, the description provides enough scope clarity and even differentiates backup volumes from other listed resources. It does not describe the return shape, but the low complexity and linked documentation mitigate that gap.

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 is empty with 100% schema description coverage, so no parameter semantics are needed. The description adds nothing about parameters, but none exist; this matches the baseline 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 uses a specific verb ('List') and resource ('Longhorn backup volumes'), with the parenthetical '(backup-target-side volume records)' clarifying the exact scope. This distinguishes it from plain volume lists, though it does not explicitly name sibling tools like volume_list or backup_list.

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 guidance on when to use this tool versus backupvolume_get, volume_list, backup_list, or other list operations. The Longhorn docs link provides reference material but no selection criteria, leaving the agent to rely on name inference.

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