qemu_vm_restore

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

Annotations already include destructiveHint=true, but the description adds a key behavioral consequence: the VM remains locked by the session and requires vm_unlock. This is valuable context beyond the annotations, though it does not detail other side effects.

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?

Two sentences, each earning its place: the first defines the operation, the second states a critical post-condition. No unnecessary words 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?

The description covers the core action and lock behavior, but lacks parameter guidance and does not direct the user to qemu_vm_trash_list to find VM IDs. For a simple one-parameter tool, it is partially complete but has clear gaps.

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?

The description provides no information about the vm_id parameter. With 0% schema coverage, the agent has no guidance on what value to supply or how to discover it, leaving the parameter completely unexplained.

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 (restore), resource (managed VM), and source (broker trash). It distinguishes from siblings like qemu_vm_trash_empty and qemu_vm_snapshot_restore by specifying 'from broker trash' and mentioning the lock behavior.

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 implies use when you want to recover a VM from trash and provides a concrete follow-up action (call vm_unlock). However, it does not explicitly mention alternatives like qemu_vm_trash_list for finding the vm_id, so it lacks exclusions but gives clear context.

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