nex_browser_click

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

No annotations are provided, so the description carries the full burden and falls short: it doesn't say whether the click auto-waits, scrolls into view, what happens with a stale snapshot ref, or whether a fresh snapshot is returned. Only the negative CAPTCHA constraint is disclosed.

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 sentences, front-loaded with the core action, and the CAPTCHA warning is compact. The CAPTCHA sentences consume roughly half the text for a side concern, but they are actionable rather than 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?

With no annotations, no output schema, and five parameters, the description should say more about failure modes (missing element, expired ref) and post-click behavior. It does add valuable cross-tool CAPTCHA workflow context, which partly compensates.

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 60% and the description only implicitly maps to 'doubleClick' via 'Click or double-click'. The 'button' parameter (left/right/middle) is an undescribed enum in both schema and description, and pageId/sessionId defaults are covered only by the schema.

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?

States a specific verb pair ('Click or double-click') and resource ('an element'), plus the two accepted target forms: snapshot ref or CSS selector. It distinguishes itself implicitly from nex_browser_mouse_click_xy by targeting elements rather than coordinates, but never names that sibling explicitly.

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 CAPTCHA guidance is genuinely useful routing ('start with nex_browser_captcha_prepare', plus an explicit do-not list of workarounds). However, it says nothing about when to prefer this over nex_browser_mouse_click_xy, hover, or check/uncheck, and gives no prerequisite that the element must come from a fresh snapshot.

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