vm_migrate

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

The description fully discloses behavioral details: it is a write operation with medium risk, records the source host for undo, and dry_run prevents recording. It adds context beyond annotations (which are absent), covering the undo mechanism and preview behavior.

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, starting with an action line, then a behavioral note, followed by parameter definitions. Every sentence adds value, and the structure is easy to parse.

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?

The description covers behavior and parameters well, but lacks details on return value (no output schema) and prerequisites like VM state or permissions. Given the tool's complexity and absence of output schema, it is nearly complete.

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?

With 0% schema coverage, the description compensates entirely by explaining each parameter: vm_id (UUID from vm_list), host_id (UUID from host_list), dry_run (preview, no undo), and target (optional, defaults). This adds critical meaning beyond the schema's type-only information.

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 action ('Live-migrate a VM to another host'), resource (VM), and scope. It distinguishes from sibling tools like vm_start, vm_stop by specifying live migration across hosts and mentioning the inverse operation.

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 provides context for use (live migration, undo via inverse) and explains the dry_run parameter for preview. However, it does not explicitly state when this tool should be used over alternatives (e.g., vm_reboot, snapshot_revert) or when not to use it.

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