pdm_pve_qemu_remote_migrate

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

With no annotations, the description carries full burden. It discloses mutation, destructive behavior (delete=True), and dry-run-by-default (PLAN). It also notes required mappings. However, it omits authorization needs, rate limits, and what happens to the source VM.

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?

Three sentences, each earning its place. Front-loaded with 'MUTATION' and core purpose. Efficient with examples and defaults.

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?

An output schema exists, so return values need not be described. But lacking prerequisites (e.g., network connectivity, PDM registration), and not all parameters are explained. For a complex migration tool, more detail would improve completeness.

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 only 10% (only proximo_target has description). The description adds meaning for target_bridge, target_storage, delete, confirm (40% of 10 params). It provides examples but leaves parameters like vmid, remote, target_remote, online, target_vmid unexplained.

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?

Description clearly states 'migrate a VM to a DIFFERENT PDM-registered remote (datacenter-to-datacenter)', distinguishing it from sibling tools like pdm_pve_qemu_migrate (same-cluster) and pdm_pve_lxc_remote_migrate (LXC). The verb 'migrate' and resource 'VM' are explicit.

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 mentions that target_bridge and target_storage mappings are required, and that dry-run is default with confirm=True to submit. It implies cross-datacenter use but does not explicitly contrast with same-cluster migration alternatives, leaving some ambiguity.

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