switch_tab

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

No annotations provided, so description carries full burden. It only says 'switch to a specific tab' without disclosing behavioral traits like whether the action is reversible, permission requirements, or how invalid indexes are handled. Minimal safety context.

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 well-structured with sections but includes a full return format that might be redundant since there's no output schema. Still concise overall with only 7 lines of substantive content.

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 switch tool, the description includes prerequisite (get_tabs) and return format, but lacks error handling details or what happens with out-of-bounds indices. Adequate but not comprehensive.

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?

With 0% schema description coverage, the description compensates by defining both parameters: session_id as 'Active browser session identifier' and index as 'Index of the tab to switch to'. This adds essential meaning beyond the raw 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?

The description clearly states the verb ('switch') and resource ('browser tab') with specificity about using index. It distinguishes from siblings like get_tabs (listing) and open_new_tab (creating) by focusing on moving between existing tabs.

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 explicitly advises calling get_tabs first to understand available indexes, providing clear when-to-use guidance. While it doesn't explicitly mention when not to use, this advice covers the main usage context.

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