qemu_mouse_click

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

With annotations offering no useful hints (all false), the description carries the full burden. It discloses the lock side effect, the unlock requirement, and the QMP mechanism, which are essential behavioral traits beyond what the schema or annotations provide.

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, front-loaded with the action and context, followed by the lock warning. Every sentence earns its place with no 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 simple click tool with no output schema, the description adequately covers the usage context (pre-Windows) and the lock/unlock lifecycle. It doesn't explicitly mention that the coordinates are zero-based, but that is in the schema, so no critical gap remains.

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 adds no parameter-specific information. The schema already covers x and y with descriptions and button with an enum/default, while vm_id is inferable from its name. With 50% schema coverage, there is no significant gap, but the description does not enhance understanding of any parameter.

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: 'Move then click through QMP' and provides the specific context 'before the Windows controller is available.' This distinguishes it from siblings like qemu_mouse_move (move only) and mouse_click (generic), making its purpose unambiguous.

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 explicitly states when to use the tool ('before the Windows controller is available') and gives a critical follow-up instruction ('call vm_unlock when finished'). While it doesn't name alternative tools, the timing condition and lock reminder provide strong usage guidance.

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