pve_disk_move

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

Despite no annotations, the description discloses key behaviors: mutation, dry-run with plan, confirm flag, delete_source as high risk, and async return of a UPID. It could clarify the default behavior of delete_source but overall adds significant value over the schema.

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 sentences, front-loaded with key info: purpose, dry-run, plan, confirm, async. Every sentence contributes essential guidance.

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 8 parameters and no annotations, the description covers only basic workflow and risks. It omits parameter details, expected inputs, and the meaning of the task UPID. Minimal viable for understanding the high-level operation.

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 only 13%, but the tool description only adds meaning for delete_source and confirm. It does not describe the required parameters vmid, disk, or target_storage, nor optional ones like kind, node, or proximo_target.

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 moves a guest disk to another storage, with verb 'move' and resource 'guest disk'. It is distinct from siblings like pve_disk_resize (resize) and pve_clone (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?

The description explains the dry-run default and the need for confirm=True to execute, providing a clear workflow. However, it does not explicitly distinguish when to use this tool versus related tools like pve_disk_resize or migration tools.

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