browser_tabs

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

No annotations are provided, so the description must carry the full burden of disclosing behavior. It does not state that closing tabs is destructive, that selecting changes the active tab, that new opens a blank tab, or what list returns. The description is behaviorally opaque.

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 short, but shortness here is under-specification rather than effective conciseness. It conveys almost no operational information and does not earn 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?

With no annotations, no output schema, and a multi-action tool, the description is critically incomplete. An agent cannot determine return behavior, side effects, or preconditions, and the tool is not distinguishable from its many siblings based on this description.

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?

The input schema fully documents both parameters, including the action enum and the index description, so the schema covers the semantic baseline. However, the description itself adds no parameter meaning beyond what the schema already provides.

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 'Manage browser tabs' is essentially a restatement of the tool name and provides no specific verb or scope. It does not mention the distinct actions (list, new, close, select) or how this tool differs from browser navigation or snapshot tools.

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?

There is no guidance on when to use this tool versus browser_navigate, browser_snapshot, or other sibling tools. The description gives no context about tab management being the right choice for opening, closing, switching, or listing tabs.

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