browser_tabs

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

With no annotations, the description carries full burden. It names actions but fails to disclose side effects (e.g., close is irreversible, select changes current tab) or that the action enum uses 'new' instead of the described 'create'. Minimal transparency beyond the obvious.

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 short sentence with zero filler. Every word adds meaning, and it's appropriately sized for a tool with a small, enum-driven schema.

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 2 parameters, no output schema, and multiple mutation actions, the description is too terse. It doesn't explain what 'list' returns, what 'new' creates (URL?), or how index selects a tab. An agent would still need to infer crucial behavior.

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 0%. The description doesn't mention the 'index' parameter or how it applies to actions like select/close. The 'create' wording conflicts with the enum value 'new', adding confusion rather than clarifying parameter semantics.

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 uses specific verbs (list, create, close, select) plus the resource 'browser tab', clearly distinguishing it from sibling tools like browser_click or browser_navigate. It captures the tool's full scope in a single sentence.

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 gives no guidance on when to use this tool versus alternatives. It doesn't mention scenarios where browser_navigate or browser_close might be more appropriate, nor any prerequisites or exclusions.

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