pve_storage_config_list

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

The description clearly states the tool is read-only, lists the returned fields (IDs, types, paths, server addresses), and mentions the source (storage.cfg). With no annotations, the description carries the full burden, and it adequately covers the core behavior, though it could mention if results are cached or any rate limits.

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 extremely concise, consisting of two short sentences that front-load the purpose and safety, then detail output and alternatives. 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 simple function of listing storage definitions, the description covers what it does, what it returns, and how to get more details. The presence of an output schema further reduces the need to describe return values. The description is complete for an agent to decide and invoke correctly.

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 has one optional parameter (proximo_target) with 100% description coverage. The description does not add extra meaning beyond the schema, which is acceptable given the parameter's self-explanatory nature.

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 all storage definitions from storage.cfg cluster-wide, specifies it is read-only with 'READ-ONLY' and 'No state change', and distinguishes from sibling pve_storage_config_get for fetching a single configuration.

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 indicates when to use this tool (listing all storage definitions) and when to use an alternative ('Use pve_storage_config_get to fetch a single storage'), plus it clarifies the operation is read-only and has no state change.

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