pve_storage_config_get

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

No annotations are provided, so the description carries the full burden. It declares the tool as 'read-only', which is sufficient for a retrieval operation. No side effects or additional behavioral traits are disclosed, but none are expected for a simple GET.

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?

Two concise sentences that front-load the main purpose and include a direct reference to the sibling tool. No redundant information.

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 low complexity (2 parameters, simple read), the description covers the essentials: what it does, what it returns, and how to list all. An output schema exists, so return details are handled. Minor improvement would be noting error behavior, but still adequate.

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 50%, with only the 'proximo_target' parameter having a description. The 'storage' parameter lacks a description in the schema, and the tool description only implies it is a storage ID without additional meaning (e.g., format, source). The description does not compensate adequately.

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 verb 'Retrieve' and the resource 'a single storage definition from storage.cfg by storage ID'. It distinguishes from the sibling tool 'pve_storage_config_list' which is for enumeration, making the purpose unambiguous.

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?

Mentions to use 'pve_storage_config_list' for enumeration, providing an alternative. However, it does not explicitly state prerequisites or when to avoid using this tool, though the context is clear.

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