pve_node_storage_backend_list

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

No annotations exist, but description marks it as read-oriented and notes smoke-confirmed response shape (not live-verified). Adds HTTP path for transparency. Lacks detail on error handling or auth, but sufficient for basic behavior.

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?

Three short, informative sentences, no fluff. Front-loads purpose and constraints. Highly efficient.

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?

Output schema exists, so return values are covered. Description provides key endpoint and smoke-test note. Could mention error cases (invalid backend), but overall adequate for a list tool with constraints.

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 33%, but description adds valid values for 'backend' (enum-like constraint), compensating for schema lacking descriptions. 'node' is implied but not elaborated; proximo_target has schema description.

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?

Description clearly states verb (list), resource (storage backends of a type on a PVE node), and indicates read-only action. Provides valid backend enum values, distinguishing 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?

Clearly states the backend types that can be listed, implying when to use this tool. Does not explicitly mention when not to use or alternatives, but sibling context makes it evident.

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