browser_click

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool scrolls the element into view and waits for it to be clickable, which goes beyond the bare action of clicking. It does not mention failure behavior on timeout or missing elements, but the key behavioral traits are covered.

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 concise sentences with no filler. The primary action and key behavioral details are front-loaded, and the fallback guidance is placed second without undermining the main purpose.

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?

For a simple one-parameter tool, the description is complete: it explains what happens (scroll, wait, click), how the target is identified, and what to do when this tool is not appropriate. The presence of an output schema covers return-value details, so no further explanation is needed.

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 0%, so the description must compensate. It does by clarifying that the selector is a CSS selector and that the click targets the first matching element. This adds meaningful context to the otherwise bare 'selector' property, though an example or further selector syntax detail would be even more helpful.

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 states a specific action (Click) and resource (first element matching a CSS selector). It also distinguishes itself from the sibling tool browser_click_at by contrasting selector-based clicking with coordinate-based clicking, making the tool's purpose immediately clear.

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 explicitly says when to use this tool versus browser_click_at: use browser_click_at when no selector can describe the target, using coordinates from browser_snapshot. This provides clear decision guidance and a named alternative.

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