mouse_click_xy

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

With no annotations, the description must disclose behavioral traits. It only says 'Click' but doesn't explain if mouse moves first, whether events are fired, or if coordinates are absolute. The button parameter suggests multiple buttons but no details.

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?

Extremely concise single sentence with no waste. However, it could include critical details while remaining succinct.

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?

Given 3 parameters (2 required), no schema descriptions, and no annotations, the description is insufficient. It omits coordinate system, button options, and output (output schema exists but not mentioned).

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 coverage is 0%, and the description adds no meaning to parameters. 'x', 'y', 'button' are not explained (e.g., coordinate origin, allowed button values). The default 'left' is in schema but not elaborated.

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 'Click at raw viewport coordinates', specifying the verb (click) and resource (viewport coordinates). It distinguishes from sibling tools like 'click', 'click_at_corner', 'click_at_image', etc., which use selectors or other targeting methods.

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?

No guidance on when to use coordinate-based clicking vs alternative click tools (e.g., element-based). No context on prerequisites or scenarios where this tool is preferred.

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