browser_tabs

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

With no annotations, the description carries the behavioral disclosure burden. It does state the direct effects of each operation ('create', 'close', 'select'), but it omits important behavioral detail such as return values for 'list', what happens if the active tab is closed, or how selection affects the active tab. This is adequate but not rich.

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, tightly packed sentence with a clear noun phrase ('Manage browser tabs') followed by a colon-delimited list of operations. There is no fluff or redundant restatement; every clause earns 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?

The tool is simple, but with no output schema and no annotations, the description should ideally mention what 'list' returns and note that 'index' is effectively required for 'close' and 'select' despite not being in the schema's required list. The current text is minimally viable but leaves these operational details implicit.

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 100%, so the baseline is 3. The description adds 'optionally at a URL' for create, but this mirrors the schema. It does not add new semantic information beyond describing the operations that use 'index' and 'url'.

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 states a clear resource ('browser tabs') and specific operations ('list', 'create', 'close', 'select'), each with concrete behavior. This separates it from sibling tools like browser_navigate and browser_close, which target page navigation or the browser itself.

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 opening 'Manage browser tabs' plus the enumerated operations clearly signal when to use this tool: whenever a tab-level action is needed. It does not explicitly name alternatives or exclusions, but the context is unambiguous and provides enough guidance for an agent to route tab operations here.

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