Left Click

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description does not contradict the annotations and adds the target scoping ('bound element or frame coordinate'), but it does not explain side effects or what happens to the UI state after the click.

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?

The description is one short sentence with no filler. Every word contributes: it states the action and the two valid target kinds, making it easy to scan and immediately actionable.

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 the schema and annotations, the description is adequate but thin. It does not help an agent distinguish when a simple left click is preferred over related sibling tools, and it leaves 'return_state' and strategy selection to the schema alone. Overall it is serviceable but not fully contextual.

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 description summarizes the two target variants ('bound element or frame coordinate') which helps clarify the 'target' parameter. However, it adds nothing about 'strategy', 'modifiers', 'return_state', or 'app_ref', and with 60% schema coverage the description only partially compensates for gaps.

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 names a specific verb ('Click') and clearly scopes the resource to 'a bound element or frame coordinate.' This distinguishes it from sibling mouse actions like 'left_click_drag', 'double_click', and 'right_click', though it does not explicitly name those alternatives.

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?

There is no guidance about when to use this tool versus siblings like 'double_click', 'right_click', or 'left_mouse_down'. The intended use for a single left click is only implied by the tool name and description, with no exclusions or alternative recommendations.

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