pve_storage_status

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

The description discloses it is read-only and lists return fields (total size, used space, free space, enabled status). With no annotations, it covers the key behavioral aspect, though it omits potential error conditions or authorization needs.

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 with two sentences, front-loading the purpose and providing essential details without extraneous 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?

The presence of an output schema covers return values, and the description adequately lists what is returned. It also references the relevant sibling tool for further actions, making it contextually complete for a read-status tool.

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 only 33% (proximo_target described). The description adds no parameter details beyond the schema, failing to explain 'node' or 'storage' parameters, which is a gap given the low coverage.

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 reads a storage backend's capacity and state (read-only), with a specific verb 'Read' and resource. It differentiates from sibling pve_storage_content by pointing to it for listing contents.

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 explicitly states when to use (read capacity/state) and directs to pve_storage_content for listing stored items, providing clear guidance on alternatives.

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