click

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

With no annotations, the description discloses scrolling into view and clicking at center for selector mode, and using CSS pixels for coordinates. However, it does not mention whether the click triggers events, if it is left-click only, or potential side effects.

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 a single sentence that efficiently conveys the essential information without extraneous words, and the key aspects are front-loaded.

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 tool's simplicity and lack of output schema, the description covers the main behavior and parameter interactions. It is nearly complete, though it omits return value or error handling details.

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 100%, but the description adds value by clarifying the relationship between selector and coordinates, and explaining the scrolling and center-click behavior for selector mode.

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 what the tool does: clicking in a renderer page, either by CSS selector (scrolled into view and clicked at center) or by raw CSS-pixel coordinates. It specifies the two distinct modes of operation.

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?

The description implies usage scenarios (selector vs coordinates) but does not explicitly guide when to use this tool over sibling tools like query_selector or other interaction tools. No exclusions or alternatives are mentioned.

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