mouse_click

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

The description adds meaningful behavioral context beyond the annotations: it discloses that the VM remains locked by this session and that the caller must unlock it. This is not captured by readOnlyHint, destructiveHint, or idempotentHint, and no contradiction exists.

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 deliver the core action, the coordinate fallback behavior, and the lock responsibility with no wasted words. The most important usage constraint is included succinctly.

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 is reasonably complete for a simple click operation, especially the lock-handling note, but it leaves out return behavior, error conditions, and any rationale for choosing this over qemu_mouse_click. Given the absence of an output schema and the number of parameters, some additional context would help.

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 covers x, y, and vm_name with descriptions, so the description's clarification that omitted coordinates use the current pointer position adds value. However, button, click_count, and interval_ms are not explained beyond defaults/enums, and the description does not compensate for the 50% schema coverage gap.

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: click at supplied coordinates, or at the current pointer position when coordinates are omitted. It is specific about the resource and behavior, though it does not differentiate from the closely related sibling qemu_mouse_click.

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 usage within a locked VM session by noting that the VM remains locked and that vm_unlock should be called afterward. However, it does not explicitly state when to prefer this over alternatives such as mouse_down/mouse_up or qemu_mouse_click.

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