browser_tabs

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds no extra behavioral context. It does not explain that closing a tab is irreversible, that creating a tab navigates to the given URL, or that selecting a tab changes focus. For a tool with destructive operations, this is minimal disclosure beyond what annotations provide.

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 sentence listing all four actions. It is concise and front-loaded with the purpose. However, it could be slightly more structured (e.g., separating actions or noting parameter dependencies) without sacrificing brevity.

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 has four actions, three parameters, and no output schema, the description is too minimal. It does not explain how parameters map to actions (e.g., url is only for 'new', index for 'close'/'select'), nor does it describe return values or side effects. The destructiveHint=true suggests more warnings are needed, but none are provided.

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%, and the parameter descriptions in the schema already explain the meaning of url, index, and action. The description adds no new semantic information about parameters. Baseline 3 is appropriate as the schema carries the full burden.

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 tool does four specific operations on browser tabs: list, create, close, or select. This distinguishes it from sibling tools like browser_navigate (which navigates a page) or browser_close (which likely closes the entire browser). The verb-resource pairing is precise and 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 when to prefer browser_tabs over browser_navigate for navigation, or over browser_close for closing the browser itself. There is no 'when not to use' or comparison to sibling tools, leaving the agent to infer usage context.

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