Move VM disk

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

Annotations indicate readOnlyHint=false (modifies) and destructiveHint=false, but the description does not clarify behavior beyond 'move'. It lacks details on prerequisites (e.g., VM must be stopped), whether source disk is deleted, or error conditions. No contradiction with annotations but insufficient context.

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?

Two efficient sentences: first states action, second gives use case. No fluff, front-loaded with key 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?

Provides basic purpose and use case but lacks details on prerequisites, default behavior of delete_source, error states, or output. Adequate for a simple tool but not comprehensive.

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 50% (3 of 6 params described: disk, storage, delete_source). The description adds no parameter details. Node, vmid, and format are undocumented in both schema and description, missing critical context for those params.

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?

Title 'Move VM disk' and description clearly state the action: moving a VM's disk to a different storage pool. It distinguishes from siblings like migrate_vm (whole VM) or move_container_disk (container).

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?

Description mentions usefulness for 'migrating off slow disks or balancing storage', providing clear context for when to use. It does not explicitly state when not to use or list alternatives, but the context is sufficient.

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