proxmox_guest_disk_move

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

No annotations are provided, so the description must cover behavioral traits. It only states 'Move guest storage' and 'requires elevated permissions,' but fails to disclose side effects like potential downtime or the default behavior of deleting the source disk (default: true in schema). The mutation and destructive potential are not explicitly addressed.

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 a single concise sentence that communicates the essential information without any fluff. Every word earns its place.

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 (6 parameters, no output schema), the description lacks critical context about prerequisites (e.g., VM must be stopped), whether the operation is synchronous, and the default delete behavior. The schema covers some details, but the description should at least hint at these aspects to be complete.

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%), and the description adds value by clarifying the 'type' parameter (VM vs LXC). For other parameters, the schema descriptions are sufficient, so the description does not need to repeat them. Overall, it provides meaningful additional context for the key distinguishing parameter.

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 (move), resource (guest storage), and specifies the applicable types (VM or LXC container), distinguishing it from sibling tools like proxmox_guest_disk_resize.

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 notes that elevated permissions are required but does not provide guidance on when to use this tool versus alternatives (e.g., disk resize, disk attach). No explicit when-not-to-use or alternative names are given.

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