click

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

With no annotations, description adds value by mentioning 'human-like move' and 'stealth (trusted-event) mode', but lacks details on default behavior, error handling, or interaction between x/y and ref.

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?

Single sentence packs key information (action, target options, variations) without fluff; slightly dense but effective.

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?

Moderate complexity (6 params, no output schema) not fully addressed; missing prerequisites, order of operations, and result description.

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?

With 0% schema description coverage, the description explains most parameters (button, double, stealth, ref, x/y) but is vague on how x/y and ref relate and lacks detail on all parameters.

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 tool performs a human-like move and click on an element or coordinates, and distinguishes from sibling tools like hover, move_to, and click_text by mentioning button options, double-click, and stealth mode.

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 this tool vs alternatives like click_text or hover; no context on prerequisites or exclusions.

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