nex_browser_open

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

With no annotations, the description carries the behavioral disclosure burden. It reveals that the tool returns per-window status and supports batch-start behavior, but it doesn't mention side effects, prerequisites, or error handling. The 'Start' verb implies launching, but more detail would be beneficial.

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 concise sentences: the first states the core purpose, the second provides targeted usage guidance. No wasted words, and the most important information is front-loaded.

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?

For a tool with two parameters and no output schema or annotations, the description covers the main purpose and batch-start use case but omits prerequisites (e.g., whether windows must pre-exist), teamId semantics, and what 'per-window status' entails. It's adequate but has gaps.

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 50% (only windowId is described). The description adds value by explaining the batch-start intent for arrays, but teamId remains undocumented both in the schema and description. It reinforces the schema's windowId semantics without adding much beyond the batch context.

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 'Start NexBrowser environments and return per-window status', using a specific verb and resource. It distinguishes from siblings like create or connect by focusing on starting environments and returning status, though it doesn't explicitly contrast itself with those alternatives.

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?

Provides explicit guidance for multi-window tasks: 'pass every window ID in one windowId array so Desktop can batch-start and tile them before creating automation sessions.' This gives clear when-to-use context, though it doesn't explicitly mention when to use alternatives like connect or create.

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