click

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

No annotations provided; description adds Retina coordinate conversion but lacks details on blocking behavior, failure modes, or off-screen coordinates.

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 short sentences that state purpose and provide a critical hint, with no unnecessary words.

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?

Simple tool with no output schema; description covers main functionality and coordinate system. Could mention input validation or immediate nature, but adequate.

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 covers all 4 parameters with descriptions (100% coverage), and the description adds extra value by clarifying coordinate conversion for Retina displays, which isn't in the schema.

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?

Clearly states the action 'Click at screen coordinates (in points)' and distinguishes from siblings like move_mouse and click_ui_element by specifying coordinate-based clicking with Retina conversion hint.

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?

Gives practical advice to 'use screenshot to determine positions' but does not explicitly exclude scenarios or mention alternatives like click_ui_element for UI-based clicks.

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