qemu_snapshot_create

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

The description adds the important behavioral detail that the VM remains locked by the session and requires vm_unlock. This goes beyond the annotations, which only indicate destructiveHint=true. It also specifies that the snapshot is internal and qcow2, adding technical context.

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 two short sentences, with the primary action front-loaded. It contains no redundant information and every sentence adds value.

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 key operational context: precondition (VM stopped), locking behavior, and required unlock call. It does not describe return values or error handling, but the tool is simple enough that this is acceptable given the annotations.

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 input schema has 0% description coverage, so the description must clarify parameter semantics. It implies 'name' via 'named snapshot' and 'vm_id' via 'VM', but does not explicitly define either. The parameter meanings are inferable from context, but not fully explicit.

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: 'Create a named qcow2 internal disk snapshot while the VM is stopped.' This distinguishes it from sibling tools like qemu_snapshot_delete, qemu_snapshot_restore, and qemu_snapshot_list by specifying creation and the snapshot format.

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 sets an explicit precondition ('while the VM is stopped') and provides a follow-up instruction ('call vm_unlock when finished'). This gives clear context for when to use the tool, though it does not explicitly name alternatives or exclusions.

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