pve_list_storage

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'List configured storage' implies a read-only operation but doesn't specify whether this requires authentication, what format the output takes, whether results are paginated, or if there are any rate limits. The description is minimal and lacks important operational context.

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 maximally concise at just three words. It's front-loaded with the essential information (list storage) and contains no unnecessary verbiage. Every word earns its place in this extremely efficient description.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'configured storage' means in this context, what information the listing returns, or how this differs from other storage-related tools in the extensive sibling list. The minimal description leaves too many contextual questions unanswered.

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 description mentions no parameters, while the schema has one optional parameter ('type' for filtering). With 100% schema description coverage, the schema adequately documents the parameter. The description adds no value beyond what's in the schema, meeting the baseline score of 3 for high schema coverage situations.

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 'List configured storage' clearly states the action (list) and resource (configured storage), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'pve_get_storage' or 'pve_list_node_storage', which appear to serve similar listing functions in this Proxmox VE context.

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. With multiple storage-related listing tools in the sibling list (pve_get_storage, pve_list_node_storage, pve_list_node_storage_content), the agent has no indication of which tool to choose for different storage listing scenarios.

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