pve_node_storage_backend_list

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

Discloses read-only behavior, return format differences per backend (VG-tree dict vs list), and verification status (PVE 9.2). No annotations exist, so description carries full burden and fulfills it well.

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?

Description is concise (3 sentences) with key information front-loaded (READ-ONLY, action). No unnecessary words; every sentence adds value.

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?

Given the tool's complexity (list operation, optional param, output schema exists), description covers purpose, behavior, return format, and alternatives completely. Agent can safely decide to use it.

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?

Schema coverage is 100%, so baseline is 3. Description reiterates backend enum values already in schema but adds no new semantics beyond what schema provides. No extra value for parameters.

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 the tool lists storage backends on a PVE node, specifies valid backend types (lvm, lvmthin, zfs, directory), and distinguishes it from sibling create/delete tools.

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?

Explicitly states when to use (list backends) and when not to (create/destroy), providing direct references to alternative tools. Also clarifies read-only nature.

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