nex_browser_connect

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful traits: default team selection, isolated session creation, startIfNeeded opening a closed window, and ordering constraints after a batch open. It omits side effects such as what happens if the window is already connected, whether the call is idempotent, and what session state is returned.

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?

Front-loads the default-routing rule, then the mechanics, then the multi-window pattern, then the CAPTCHA constraint. Every sentence contributes, though the CAPTCHA prohibition is somewhat tangential to a connect tool and lengthens an otherwise tight definition.

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 and no output schema, the description should cover more about what a successful connect produces and how failures surface (for example, a window that cannot be started). It covers usage comprehensively but leaves the post-connect state and error behavior to inference.

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 67%, and the one uncovered parameter is the required windowId, whose meaning is only inferable from 'connect each' in the multi-window sentence. The description adds genuine meaning beyond the schema for startIfNeeded (batch-then-connect ordering) and teamId (active team by default), which the schema notes only tersely.

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 and resource: 'Connects one window (active team by default) and creates an isolated automation session.' It also implicitly distinguishes itself from nex_browser_open, which is named for the multi-window opening step, so an agent can separate the two. What 'connecting' actually yields (a session handle, a readiness state) is not spelled out, keeping it short of a 5.

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?

Explicitly declares this the default for nexbrowser-mcp browser tasks, gives the exact multi-window sequence (call nex_browser_open once with all IDs, then connect each with startIfNeeded=false), and routes CAPTCHA work to nex_browser_captcha_prepare. It also states a negative rule: do not solve CAPTCHAs with CDP, Python, image matching or scripted drags.

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