nex_browser_tab_new

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says a new tab is opened and may be navigated, but it does not explain whether the new tab becomes active, what happens to the current session/tab, whether any permissions are required, or what the tool returns.

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, front-loaded sentence with zero filler. It is appropriately sized for the limited information it conveys.

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?

This is a browser-automation tool with no annotations and no output schema. The description is too thin to fully equip an agent to invoke it correctly: it omits tab/session state effects, optional-URL behavior, and return-value expectations.

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 only 50%: sessionId is already documented in the schema, while url is undocumented. The description partially compensates by clarifying that url is optional and acts as the navigation target, but it does not add URL format details or sessionId interaction behavior.

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 states a specific verb and resource: "Open a new tab" plus optional navigation. This is clear enough to identify the action, but it does not distinguish the tool from nearby siblings such as nex_browser_tab_select, nex_browser_tab_list, or nex_browser_navigate.

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 implies you should use it when a new tab is needed, but it gives no explicit when-to-use guidance, prerequisites, or alternatives. It never says when not to use it versus nex_browser_navigate or nex_browser_tab_select.

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