mouse_click

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

Adds a critical behavioral detail beyond annotations: the VM remains locked by this session and must be unlocked with vm_unlock. This is essential for the agent to avoid leaving the system in a locked state. It also clarifies the optional coordinate behavior, which annotations do not convey.

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 core action, and no wasted words. The VM lock warning is placed appropriately after the primary function.

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?

Covers the core behavior and the critical VM lock/unlock context. It could mention click_count or the physical coordinate system, but the schema already handles some of that, and the tool is relatively simple. Overall, it is sufficiently complete for an agent to use safely.

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?

Schema description coverage is only 40%, and the description partially compensates by clarifying coordinate optionality. However, it does not explain the semantics of button, click_count, or interval_ms, leaving gaps that the schema does not fully fill.

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), the resource (mouse), and the flexibility of using either supplied coordinates or the current pointer position. This sharply distinguishes it from sibling tools like mouse_down, mouse_up, mouse_move, and mouse_drag.

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?

Provides clear context for when to use this tool, including the ability to omit coordinates for the current pointer position. It also notes the VM lock requirement, but it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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