browser_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. The verb 'List' implies non-mutating read-only behavior and the field enumeration adds some value. However, it does not disclose ordering, whether the list spans all browser contexts, or whether any side effects apply; the description is adequate for a simple list tool 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 one short sentence that immediately gives the operation and the returned fields. Every word earns its place and no structured data is repeated.

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 no parameters and an output schema exists, the description covers the necessary invocation details for an agent. The main gap is the lack of explicit context about which tabs are considered 'open' and whether tab ordering is relevant, but this is minor for such a low-complexity, no-parameter 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?

The input schema has zero parameters, so the description does not need to compensate for parameter documentation; it correctly focuses on return content instead. Since there are no parameters to explain, the baseline of 4 is appropriate.

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 specific verb and resource ('List open browser tabs') and specifies exactly what is included in the result ('index, title and URL'). This is clearly distinguishable from sibling tools like browser_navigate or browser_snapshot, and there is no tautology or ambiguity about its scope.

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 offers no guidance on when to use this tool versus alternatives such as browser_status, browser_snapshot, or browser_tab_new, and no mention of browser context scope (e.g., current window vs all windows). The tool should either be paired with explicit when-to-use guidance or explicit exclusions, but none are present.

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