Move Guest Disk

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to restate those. The description adds one useful behavioral fact: elevated permissions are required. However, it does not disclose that the move may delete the source disk by default or that the operation is a live storage migration, relying on the schema's delete parameter and the destructive annotation to carry that weight.

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 sentence with no filler and front-loads the primary action. The parenthetical 'type=vm' and 'type=lxc' is somewhat redundant with the schema enum, but it is compact and useful. It earns a high score for brevity without losing core 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 destructive annotation, high schema coverage, and no output schema, the description is minimally viable: it states the action, target resource types, and a permission requirement. Still, it lacks any mention of operational consequences such as source disk deletion by default or expected task behavior, which would help an agent fully anticipate the outcome.

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 description coverage is 83%, and the schema already documents parameters such as disk examples, node, vmid, storage, and the delete default. The description only restates the type enum values and adds the permission note, providing no new parameter-level meaning. This meets the baseline for high schema coverage but adds little beyond it.

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 states a specific verb and resource: 'Move guest storage for VM (type=vm) or LXC container (type=lxc)'. It clearly identifies the tool's scope and the required type distinction slash target. However, it does not explicitly contrast with sibling disk/storage tools such as resize or migrate, so it falls short of full differentiation.

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 gives no guidance on when to use this tool versus alternatives like proxmox_guest_migrate or proxmox_guest_disk_resize. 'Requires elevated permissions' is a permission prerequisite, not a usage condition. There is no mention of constraints such as target storage availability or whether the guest should be stopped.

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