nex_browser_navigate

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

With no annotations provided, the description carries the full behavioral-disclosure burden. It does add useful context by stating that the return value is a refreshed accessibility snapshot and by disclosing the CAPTCHA workflow and prohibited solving methods, but it does not cover navigation waits, failure modes, session/page requirements, 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 sentences and front-loads the core action and return value. The second sentence is a targeted operational constraint rather than filler, so every part earns its place.

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?

There is no output schema, but the description explains that the refreshed accessibility snapshot is returned, which covers the main return expectation. It also covers the CAPTCHA caveat, though it leaves some navigation-specific behavioral details and parameter usage implicit.

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 67%: pageId and sessionId already document their default-to-active behavior, while url is undocumented in the schema and the description only indirectly implies navigation target. The description does not add parameter-level meaning beyond the schema, so the moderate schema coverage supports a baseline score of 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 and resource: it navigates the selected page and returns its refreshed accessibility snapshot. It is clear what the tool does, but it does not explicitly distinguish itself from nearby navigation/state siblings such as nex_browser_reload, nex_browser_open, nex_browser_go_back, or nex_browser_go_forward.

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 gives one clear usage rule: for page CAPTCHAs, start with nex_browser_captcha_prepare and avoid CDP, Python, image matching, or scripted drags. However, it does not say when to use nex_browser_navigate versus related tools like nex_browser_reload or nex_browser_open, so broader tool-selection guidance is left implied.

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