Switch Browser Tab

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

Annotations indicate mutability (readOnlyHint=false) but no destructive effects. The description adds value by warning about private/authenticated sessions, which annotations do not cover. However, it does not explicitly state that the tool changes the active tab and preserves previous tab state, which would further improve 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?

Three concise, front-loaded sentences. First sentence states purpose, second gives preconditions/next steps, third handles sensitivity. No wasted words; every sentence earns its place.

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 nested objects), the description covers purpose, preconditions, post-actions, and sensitivity. Output schema exists (not shown) but description does not need to explain it. Complete for an AI agent to correctly invoke.

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 0%, so the description must compensate. It explains that pageId must be obtained from browser_list_tabs or browser_attach_cdp, providing essential context. While it does not detail format, the source guidance sufficiently compensates for the lack of schema descriptions.

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 verb ('make a previously discovered page the active target'), specifies the resource (browser tab), and distinguishes from siblings like browser_new_tab and browser_close_tab by requiring a pre-obtained page ID and recommending a follow-up confirmation with browser_get_state.

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?

Explicitly says 'Use when a full-profile workflow must make a previously discovered page the active target', provides preconditions (obtain page ID from specific tools), and advises confirming selection afterward. Also includes a sensitivity warning about private/authenticated content, giving clear when-to-use and precautions.

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