browser_click

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

With no annotations, the description carries the full behavioral burden but discloses nothing beyond the action: no waiting behavior, scrolling, error handling, or visibility requirements. It says only 'Click an element,' which does not explain runtime behavior or 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, tightly written sentence with no filler words. It front-loads the action and scoping source ('from browser_snapshot'), making it easy to parse quickly.

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 no annotations, no output schema, and a frameSelector parameter that needs clarification, the definition is too sparse for an agent to call it reliably. Missing context includes what happens when no element matches, whether the click scrolls into view, and how timeout is applied.

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 schema already documents selector, ref, and frameSelector with useful descriptions, and the description largely restates that information. Timeout is undocumented in both schema and description, so the 75% coverage is not fully compensated, but the description adds no real semantic value beyond what the schema supplies.

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 a specific verb ('Click') and resource ('an element') with two explicit targeting methods: CSS selector or aria ref from browser_snapshot. It is unambiguous about the core action, though it does not explicitly contrast with sibling tools like browser_iframe_click.

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 when-to-use or when-not-to-use guidance is provided; the description only restates the action itself. It fails to mention when browser_click should be preferred over browser_iframe_click or why frameSelector exists in the schema, leaving usage decisions entirely to the agent's inference.

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