List backup targets

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

No annotations are provided, so the description carries the full behavioral burden. It adds only the qualifier 'configured' and a docs link; otherwise it repeats the title's verb. It does not state the read-only nature explicitly, nor describe output shape, sorting, pagination, or failure behavior. For a zero-annotation tool, this is a meaningful gap.

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?

Two short sentences with the core action front-loaded and a useful reference link appended. The docs URL earns its place as contextual material. Minor deduction because the first sentence nearly duplicates the title, a slot that could have carried differentiating or behavioral value instead.

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 near-minimally viable: an agent can invoke it correctly and understand its purpose. However, with no output schema, there is no indication of what fields a backup target contains (e.g., name, URL, availability), and no hint of when list is preferred over backuptarget_get. The docs link partially offsets these gaps.

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 zero parameters, so there is nothing for the description to document. The rubric's baseline for 0 parameters is 4, and the description correctly avoids inventing parameter details. No compensation is needed.

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 specific verb and resource: 'List configured backup targets.' The verb 'list' inherently distinguishes it from sibling operations like backuptarget_create, backuptarget_update, and backuptarget_delete. However, it largely restates the title and does not explicitly contrast with the closely related backuptarget_get, so it stops short of full sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives. Siblings include backuptarget_get and backupvolume_list, but nothing tells an agent whether to prefer this list call or a get call for a specific target. The Longhorn docs link points to general backup-and-restore documentation, not to a usage decision guide.

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