proxmox_vm_disk

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'add disk' and 'remove disk' without disclosing consequences (e.g., data loss on remove, permission requirements beyond 'elevated', or side effects like requiring VM shutdown). This is insufficient for a potentially destructive operation.

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 very short and to the point. The second sentence effectively structures the action parameter as key-value pairs. However, the first sentence ('Manage VM disks') is redundant since the tool name already implies this. It could be more informative within the same length.

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 complexity (add/remove disks), the description is incomplete. It lacks critical context such as prerequisites (VM stopped?), what happens on removal (disk destroyed?), and the fact that size is only relevant for add. No output schema is provided, but description does not explain what the tool returns. Significant gaps remain.

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 high (83%) with most parameters already described. The description adds minimal value by clarifying the action parameter's mapping from keywords to operations and hinting at elevation. However, it does not add meaning beyond the schema for other parameters like size (only for add) or storage.

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 manages VM disks and defines two actions: add and remove. This distinguishes it from sibling tools like proxmox_guest_disk_move or proxmox_guest_disk_resize. However, the initial verb 'Manage' is somewhat vague, and no explicit differentiation from siblings is provided.

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 versus alternatives (e.g., when to use this vs. proxmox_guest_disk_move). There is no mention of prerequisites (e.g., VM must be stopped) or when-not-to-use. The phrase 'all elevated' is ambiguous and does not provide clear usage context.

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