pve_migrate_vm

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral traits such as whether migration is disruptive (e.g., downtime implications), permission requirements, rate limits, or what happens on failure. For a complex operation like VM migration, this is a significant gap.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and appropriately sized for the tool's complexity.

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?

For a complex VM migration tool with 8 parameters, no annotations, and no output schema, the description is inadequate. It lacks information about behavioral implications, error handling, return values, or operational constraints that are critical for safe use.

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%, so parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond implying migration involves source and target nodes, which is already clear from parameter names. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('Migrate') and resource ('VM'), specifying the action of moving a virtual machine to another node. It distinguishes from siblings like 'pve_move_vm_disk' (which moves disks) and 'pve_clone_vm' (which creates copies), but doesn't explicitly contrast with 'pve_migrate_container' (for containers vs VMs).

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?

No guidance is provided on when to use this tool versus alternatives like 'pve_migrate_container' for containers or 'pve_move_vm_disk' for disk migration. The description lacks context about prerequisites, timing considerations, or any 'when-not-to-use' scenarios.

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