qemu_vm_unselect

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

Annotations already indicate the tool is not read-only and not idempotent, and the description adds that it clears a session-scoped selection. This is useful behavioral context, but the description does not disclose what happens if no selection is active or whether existing VM-managed state is affected beyond the selection.

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?

A single, clear sentence conveys the entire operation without filler. The key scoping information ('session's managed QEMU VM selection') is front-loaded and essential.

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 zero-parameter state-clearing tool, the description is sufficiently complete to invoke correctly. It lacks only minor behavioral details such as return/confirmation behavior and whether clearing an already-empty selection is a no-op.

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 tool has zero parameters, so the schema fully defines the input contract. The description correctly does not attempt to describe parameters that do not exist, which is appropriate for a no-argument operation.

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 uses a specific verb ('Clear') and resource ('this session's managed QEMU VM selection'), making the operation immediately understandable. It also differentiates itself from the sibling qemu_vm_select, since it is 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 implies the tool is used when the session has a managed QEMU VM selection that should be cleared, and qemu_vm_select is the obvious complementary alternative. However, it does not explicitly state when to use it versus related VM-selection tools or describe any preconditions or no-op behavior.

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