pve_node_disks_list

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

The description notes it is a read operation and includes a caveat that the response shape is not live-verified ('Smoke-confirm'), which adds behavioral awareness. However, it lacks details on required permissions, side effects, or whether the node parameter is truly optional despite being nullable in schema.

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?

Three concise lines: summary, endpoint, and caveat. Front-loaded with key purpose; no unnecessary words.

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 description covers basic purpose and endpoint, but does not explain parameter optionality, default behavior, or output structure. There is no mention of pagination or filtering. The 'Smoke-confirm' note adds some completeness regarding reliability, but overall more detail is needed for an agent to use it confidently.

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 adds context for the 'node' parameter via the URL path, but it implies it is required while the schema marks it optional (default null). No explanation of the node parameter format or meaning. The 'proximo_target' parameter is already documented in schema, so no extra value.

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?

Description clearly states 'List physical disks on a PVE node (read)', specifies the HTTP endpoint, and indicates it returns inventory and health info. This distinguishes it from other disk operations (e.g., wipe, initgpt) but does not explicitly contrast with pve_hardware_list or storage list tools.

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?

No guidance on when to use this tool vs alternatives such as pve_hardware_list, pve_storage_content, or other disk-related tools. No 'when-not' or prerequisite information provided.

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