pdm_pve_qemu_remote_migrate

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

Despite no annotations, the description thoroughly discloses behavioral traits: mutation flag at start, dry-run by default, confirm to submit, delete irreversible, and the fact that confirm returns a PDM task reference that cannot be polled with pve_task_status. It also explains the mapping format and includes examples.

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 concise (5 sentences) and well-structured: starts with purpose and mutation flag, then differentiators, required mappings, important flags, and finally the dry-run/confirm and tracking notes. Every sentence adds essential 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 tool's complexity (10 parameters, 5 required, mutation with dry-run/confirm, cross-datacenter migration), the description covers key aspects: alternatives, required mappings, flags, and post-submission tracking. An output schema exists, so return values are not needed.

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 100%, giving baseline 3. The description adds value by explaining mapping formats (e.g., 'vmbr0:vmbr0'), clarifying the irreversible nature of delete, and elaborating on the dry-run/confirm workflow, which goes beyond the schema descriptions.

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 is for migrating a VM to a different PDM-registered remote (datacenter-to-datacenter). It explicitly differentiates from siblings by noting when to use pdm_pve_lxc_remote_migrate for containers and pdm_pve_qemu_migrate for same-cluster moves.

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?

Provides explicit guidance on when to use this tool versus alternatives, mentions required mappings (target_bridge, target_storage), explains the dry-run default and confirm behavior, and advises tracking the returned task reference with pdm_tasks_list instead of pve_task_status.

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