browser_click

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action and targeting options, but omits important traits such as whether the tool scrolls the element into view, waits for the element, what happens if both selector and coordinates are provided, or that clicking may trigger navigation or other 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 two brief sentences, front-loaded with the primary action ('Click on an element'). Every word earns its place, with no redundancy or filler.

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?

The schema covers all parameters, so no parameter documentation gaps exist. However, the description lacks context on edge cases like missing elements, coordinate system assumptions, or interaction with page state, which are relevant for a browser click tool. Given the tool's apparent simplicity, it is minimally complete but not rich.

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 description coverage is 100%, so each parameter is already documented. The description adds a small semantic layer by clarifying that selector and coordinates are alternatives ('or'), but it does not specify precedence or conditional requirements, leaving the baseline at 3.

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 uses a specific verb ('Click') and resource ('element'), clearly distinguishing this from sibling tools like browser_hover or browser_type. It also states the two targeting methods (CSS selector or coordinates), making the tool's scope explicit.

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 usage is somewhat implied by the action word 'click' and the sibling tool names, but there is no explicit guidance on when to use this tool over browser_hover, browser_select, or others. 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.