nex_browser_connect

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

With no annotations, the description carries full burden. It mentions 'isolated automation session' and 'active team by default' but fails to disclose side effects, prerequisites, window startup behavior, or session lifecycle. The startIfNeeded parameter hints at behavior not covered in the text.

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 a single sentence that is front-loaded with the core action and avoids unnecessary words.

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?

Given no annotations and no output schema, the description omits important context: prerequisites (NexBrowser app running), what an 'isolated automation session' means for subsequent tool calls, and the return value or success indicators.

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% (teamId and startIfNeeded have descriptions). The description's 'active team by default' repeats what teamId's schema description already states. No additional parameter-specific context is provided for windowId or startIfNeeded.

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 a NexBrowser window) and the scope (using active team by default, creating an isolated automation session). It distinguishes from siblings like nex_browser_disconnect and nex_open_browsers, though not explicitly naming them.

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?

No guidance is given on when to use this tool versus alternatives. The description implies connection for automation but does not state exclusions or mention sibling tools like nex_browser_disconnect for teardown.

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