List system backups

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

There are no annotations, so the description must convey behavioral expectations. 'List' semantically suggests a read-only operation, and the included Longhorn docs URL offers some external behavioral context. However, the description itself does not disclose output shape, pagination, failure modes, or any specific side effects.

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, front-loaded sentence that states the purpose and then provides a helpful documentation link. Every element earns its place, and there is no wasted wording.

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, this is nearly complete: it names the resource and provides authoritative documentation. The only notable omission is a direct description of the return value, but the docs link mitigates 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 has no properties, so there are no parameters to document. With zero parameters, the schema coverage is trivially complete and the description does not need to compensate for missing parameter meaning.

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 names a specific verb ('List') and a specific resource ('Longhorn system backups'), so an agent immediately knows what the tool does. It is also distinguishable from sibling tools like systembackup_get, systembackup_create, and systemrestore_list by action and resource.

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 action 'List' implies when to use the tool, but the description gives no explicit guidance about when to prefer this over systembackup_get or other backup-related tools. There are no exclusions or alternative routing hints beyond the obvious resource name.

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