nex_browser_connect

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

With no annotations, the description carries full responsibility. It discloses that the tool creates an isolated automation session and defaults to the active team, but it does not describe side effects on existing connections, failure modes, or permission requirements. This provides some value but leaves significant gaps.

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 a clear purpose, and every word earns its place. No irrelevant detail 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?

The description covers the main workflow and multi-window orchestration, but it does not mention return values, error conditions, or what happens if the window is not running. Since no output schema exists, the description should fill that gap to be more complete.

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 covers teamId and startIfNeeded with descriptions, but windowId has no description and the description only mentions 'one window' indirectly. The multi-window workflow adds meaning to startIfNeeded, but the description does not significantly enhance parameter understanding beyond 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?

The description clearly states the action ('Connect to one NexBrowser window') and the outcome ('create an isolated automation session'). It distinguishes itself from sibling tools like nex_browser_open (which opens windows) and nex_browser_disconnect (which tears down sessions).

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 instructs to use the active team by default and provides a precise multi-window procedure: call nex_browser_open once, then connect each window with startIfNeeded=false. This is concrete when-to-use guidance, though it does not mention alternatives or when not to use.

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