List backing images

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It identifies what is being listed but does not state whether the operation is read-only, whether pagination exists, what ordering or scope applies, or what errors might occur. The docs link points to more information but does not provide inline behavioral transparency.

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 compact and front-loaded: the primary operation appears in the first sentence, and the docs link adds context without bloat. Every element contributes to the tool's purpose.

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 list operation, the description is minimally serviceable: it names the resource and links to official documentation. However, with no output schema and no annotations, it does not explain the response shape, pagination, or any list-specific caveats, leaving some inference required.

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 and the schema fully documents that, so there is no parameter semantics burden on the description. The baseline for a zero-parameter tool is therefore appropriate.

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 states a clear verb-resource pair ('List Longhorn backing images') and adds a domain docs link. It distinguishes itself from sibling get/create/delete operations by the 'list' verb, though it does not explicitly say how it differs from backingimage_get.

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 alternatives such as backingimage_get or backingimage_list_tags. An agent must infer usage from the tool name and conventional list semantics; no exclusions or selection criteria are provided.

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