List storage

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

The description mentions the output fields (type, enabled content, free space), providing behavioral insight beyond the readOnlyHint annotation. It does not disclose potential errors, permissions, or performance traits, but for a simple read-only list, the description is sufficient.

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, well-structured sentence of 12 words that immediately conveys the tool's purpose and output. Every word adds value, making it highly concise and 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?

Given the tool's simplicity (single parameter, no output schema), the description covers the essential behavior: listing storages with key attributes. It could mention if any authentication or permissions are needed, but it is largely complete for a basic list operation.

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 description coverage is 100%, and the schema already provides a clear description for the node parameter. The description's phrase 'visible from a node' reinforces the parameter but adds no new semantic meaning beyond the schema.

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 action (list), resource (storages), and scope (visible from a node). It also specifies the returned attributes (type, enabled content, free space), distinguishing it from sibling tools like pve_storage_content that list content of a storage.

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 implies that the tool requires a node parameter, but does not explicitly state when to use it versus alternatives such as pve_storage_content for storage contents. It lacks explicit exclusions or when-not recommendations.

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