browser_switch_tab

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

With no annotations provided, the description carries the full burden. It states the primary effect (switching tabs) but does not disclose any behavioral details such as error behavior, impact on the current page, or whether it works across windows. The description is minimally transparent but lacks depth.

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 with no redundant words. It is front-loaded and immediately states the action and object.

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 tool's simplicity (one parameter, no output schema), the description is adequate but not complete. It lacks context about how to obtain tab IDs or what happens on invalid IDs. However, the schema and sibling tools provide some implicit context, so the description is minimally viable.

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 already provides full coverage for the single parameter (tabId with description 'Tab ID to activate'). The description adds no additional meaning beyond restating that the tool switches to a tab by ID. High schema coverage yields a baseline of 3, and the description does not exceed it.

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 'Switch to a tab by ID' uses a specific verb (switch) and resource (tab) with a clear scope (by ID). It clearly distinguishes from sibling tools like browser_new_tab, browser_close_tab, and browser_list_tabs, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that tab IDs are typically obtained from browser_list_tabs, nor any prerequisites or conditions for switching. The context is entirely omitted.

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