Relocate a running VirtualMachineInstance to another node without restarting. Provide name and namespace to execute migration.
Live migrate a VirtualMachineInstance to another node.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| cluster | No | ||
| namespace | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action. It does not mention whether migration is asynchronous, requires special permissions, can fail for certain VMIs, or what happens to the original instance.
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?
A single sentence that is efficiently front-loaded with the action, resource, and destination. There is no filler or repetition.
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?
Although an output schema exists and return values need not be described, the tool has no annotations, no parameter explanations, and no usage context. For a mutating operation that moves a running workload, this is too incomplete to guide correct invocation.
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 does not explain any of the three parameters. It does not clarify that name/namespace identify the VMI, nor what the optional cluster setting controls or how the target node is selected.
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 uses a specific verb ('Live migrate') with a specific resource ('VirtualMachineInstance') and destination ('another node'). This clearly identifies the operation and differentiates it from sibling VM tools like start/stop/restart or drain_node.
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 about when to use migration, what preconditions apply (e.g., VMI must be running, target node availability), or how it differs from related operations such as drain_node or stop/start. The agent must infer usage entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.