qemu_snapshot_restore

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

Beyond the annotations (destructiveHint=true), the description discloses that the VM must be stopped and that the VM remains locked by this session, requiring vm_unlock. This is actionable behavioral context that the annotations do not capture.

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 efficient sentences with no extraneous words. The first sentence states the core function; the second provides necessary lock handling guidance.

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?

Given the absence of an output schema and param descriptions, the description covers the essential scenario: restore an internal snapshot, with prerequisites and follow-up. It could mention that the snapshot name must exist or that the current disk state is overwritten, but annotations cover destructiveness.

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 schema provides no descriptions for vm_id or name (0% coverage). The description adds that the snapshot is 'named' and an 'internal disk snapshot', clarifying the name parameter, but does not elaborate on parameter formats or where to find valid snapshot names.

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'), the resource ('named qcow2 internal disk snapshot'), and the condition ('while the VM is stopped'). It distinguishes from sibling tools like qemu_snapshot_delete or qemu_vm_restore by specifying internal disk snapshots.

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?

It provides clear context: the VM must be stopped and the session holds the VM lock, with a required follow-up call to vm_unlock. It does not explicitly mention alternative tools or exclusions, but the precondition and post-action are enough for basic usage.

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