manage_tabs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains what 'list' returns, what each action does, and warns that tab indexes are session-scoped and may change after tabs are opened or closed. It also notes that other browser actions may open new tabs, which helps the agent plan its calls.

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-organized with a clear opening summary, a usage boundary, an action breakdown, and a notes section. Every sentence adds necessary information, and the structure makes it easy for an agent to scan the action options and associated parameters.

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 multi-action nature and conditional parameters, the description is complete: it covers all four parameters, all five actions, return contents for list, the relationship between list and switch, and important caveats about tab index stability. The sibling-tool boundary is also explicitly drawn, so an agent can confidently select this tool.

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 0%, so the description must fully explain parameters. It does: action is detailed with each enum value's behavior, url is tied to 'open', tab_index is tied to list results for 'switch', and switch_to is explicitly described. This fully compensates for the schema's lack of 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 opens with a specific verb and resource: 'List, open, switch between, or close browser tabs.' It clearly defines the tool's scope and distinguishes it from navigate/manage_history, which manage navigation within the current tab rather than tab-level operations.

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?

It explicitly states that tab management belongs here and that browser navigation within the current tab belongs to navigate and manage_history. It also advises calling action='list' before 'switch' to determine tab_index, giving concrete when-to-use guidance.

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