nex_browser_tab_select

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'select a tab.' It does not state what selecting entails, whether it affects the active tab, what happens if the page ID is invalid, or whether it has side effects. The one-liner provides minimal behavioral transparency.

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, concise sentence that is front-loaded with the operation and resource. It contains no wasted words and is easy to scan.

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 simple selection tool, the description is extremely minimal. It lacks context about the active session, return value, or relationship to other browser operations. Given the absence of an output schema and annotations, the description does not provide enough information for an agent to fully understand the tool's role and outcomes.

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?

The schema only describes sessionId, leaving pageId undocumented. The description adds the phrase 'stable page ID' but does not explain where to obtain a page ID or what makes it stable. With 50% schema coverage, the description compensates inadequately for the missing parameter semantics.

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 (select), the resource (tab), and the key identifier (stable page ID). It unambiguously distinguishes this from sibling tools like tab_list, tab_new, and tab_close by indicating selection as the specific operation.

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 provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., obtaining a page ID from tab_list) or indicate that selection is needed before other interactions. The lack of usage context forces the agent to infer the appropriate scenarios.

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