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 states the action. It does not cover state changes (active tab switching), error handling for invalid page IDs, prerequisites (e.g., an active browser session), or return behavior, leaving the agent with minimal insight.

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 single sentence is efficient and front-loaded, but it is under-specified: it omits critical context such as usage prerequisites and expected outcomes. Conciseness here borders on incompleteness, so a mid-range score is appropriate.

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 the lack of annotations and an output schema, the description must compensate, but it does not. It fails to explain return values, error behavior, the meaning of 'stable page ID' in practice, or sessionId's optionality beyond what the schema already states.

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 description coverage is only 50% (sessionId has a description, pageId does not). The description adds minimal meaning to pageId via 'stable page ID' but does not explain how to obtain it or its format, and adds no extra value for sessionId 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?

Description uses a specific verb ('Select') with a clear resource ('a tab') and mechanism ('by stable page ID'), effectively distinguishing this tool from sibling tab operations like browser_tab_list, browser_tab_new, and browser_tab_close.

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. For instance, it does not mention that 'stable page ID' comes from browser_tab_list, nor does it explain the role of sessionId or when this selection is needed.

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