pve_migrate_vm

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

With no annotations, the description must disclose behavior on its own. It does state the action and the confirmation requirement ('Requires confirm=true'), but it does not describe side effects, downtime, source-node cleanup, or asynchronous behavior. This is moderately transparent but missing significant operational context.

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 very concise and front-loaded, with no wasted words. Both sentences carry essential information: the action and a critical requirement (confirm=true).

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 8-parameter mutation tool with no annotations and no documented behavior beyond the basic action, the description is far too sparse. The presence of an output schema helps return-value understanding, but it does not compensate for missing context about prerequisites, migration modes, storage handling, and consequences.

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 0%, and the description adds minimal parameter meaning. It only hints that 'target' corresponds to 'another node' and that confirm must be true, but it does not explain required parameters like node/vmid or optional ones like targetstorage, online, vm_type, and with_local_disks.

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's purpose with a specific verb ('Migrate'), resource ('VM/container'), and destination ('another node'). It distinguishes itself from sibling tools because no other sibling is a migration action.

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 does not explain when to choose this tool over alternatives such as clone or relocate storage. It only mentions 'Requires confirm=true', which is an invocation requirement, not contextual usage guidance.

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