qemu_vm_start

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

The description exposes the session-locking side effect and the need for vm_unlock, plus technical details (QMP, guest TCP network). Annotations only state non-readonly and non-destructive, so this adds meaningful context. It doesn't mention what happens if the VM is already running or whether the call blocks, but the lock disclosure is significant.

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 compact two-sentence structure. The first sentence names the operation and key features; the second delivers the essential locking and unlock requirement. No filler or redundancy.

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 VM start operation the description covers the primary action and the lock contract, but omits error behavior (e.g., VM already running or invalid ID), return expectations, and explicit parameter semantics. Since there is no output schema, some indication of what to expect after execution would improve completeness.

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 coverage is 0%, and the description does not explicitly explain vm_id. The only clue is the tool name and 'Start a managed QEMU VM', which allows inference, but the description should compensate by stating that vm_id must reference an existing managed VM. It does not.

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 starts a managed QEMU VM with QMP and guest TCP networking. This is a specific verb+resource and distinguishes this operation from sibling tools like qemu_vm_create, qemu_vm_shutdown, and qemu_vm_restart.

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 clear context that the VM remains locked and instructs the caller to invoke vm_unlock when finished. It does not explicitly compare against alternatives or specify preconditions like 'VM must be stopped', so it misses exclusionary guidance.

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