vm_move_disk

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

Discloses async execution, undo token recording, and dry_run behavior. No annotations provided, so the description carries the full burden; it covers essential behavioral traits without omissions.

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?

Efficiently structured with a header, a core sentence, and a clean list of parameter descriptions. No redundant or irrelevant 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?

Covers all 7 parameters, describes async behavior and return type, explains undo token and dry_run preview. No output schema exists, but the description provides sufficient context for an agent to use the tool correctly.

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?

With 0% schema coverage, the description fully compensates by explaining each parameter with examples and context (e.g., disk key format, auto-locate for node), adding significant value beyond the schema.

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?

Clearly states the action ('Move a VM disk to another storage'), identifies the return type ('task UPID'), and distinguishes from sibling operations like vm_migrate or vm_clone.

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?

Explicitly marks as [WRITE] and describes dry_run for preview, but does not provide explicit when-to-use or when-not-to-use comparisons with siblings. Still clear enough for appropriate invocation.

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