browser_click

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

With no annotations present, the description carries the full burden and does disclose important behavior: clicking returns a fresh snapshot and popups automatically become the active tab. This goes beyond a bare 'click' statement, though it does not disclose timeout behavior, error cases, or whether navigation waits for page load.

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 compact and front-loaded: the action comes first, followed by the return behavior and the popup caveat in a short parenthetical. Every phrase earns its place, with no filler or repetition.

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 two-parameter click tool, the description provides the essential action and return behavior. However, it lacks timeout_ms semantics and any guidance about selecting this over sibling input tools, so an agent has enough for a basic call but not full confidence in edge cases.

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 clarifies that n refers to an element number/index via "element #n", but it says nothing about timeout_ms, leaving a required-for-completeness parameter undocumented. The description only partially compensates for the schema gap.

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 verb and resource: "Click element #n". It also clarifies the output (FRESH snapshot) and a key behavioral consequence (popups become the active tab), making it clearly distinguishable from sibling browser_* tools like browser_press, browser_type, or browser_set.

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 use when the agent needs to click an element and then inspect the resulting snapshot, but it does not explicitly state when to use this tool versus alternatives such as browser_press or browser_form. No when-not-to-use guidance is provided.

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