Switch Tab

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

The description indicates a non-destructive switch operation, but annotations set destructiveHint=true, creating a contradiction. This misleads the agent about the tool's safety profile.

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?

A single, front-loaded sentence with no extraneous information. Every word is essential.

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?

The description omits details on success/failure behavior, prerequisites (e.g., tab must exist), and does not explain the destructiveHint annotation. With an output schema present, it is somewhat adequate but leaves gaps.

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 100%, so the description adds little beyond the schema's parameter description. The phrase 'from tab_list' provides minor context but is already implied by 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?

The description clearly states the verb 'Switch' and the resource 'active browser tab by id from tab_list', specifying the source of the tab ID. It effectively distinguishes from sibling tools like tab_list and 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?

The description implies usage when you need to switch to an existing tab identified by ID, but lacks explicit guidance on when not to use or comparisons with alternatives like tab_close or tab_list.

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