browser_listTabs

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

No annotations are present, so the description must convey safety and behavior. The verb 'List' strongly implies a read-only operation, and the description discloses the exact output fields, providing reasonable transparency for a simple query tool. It lacks explicit statements about side effects or browser requirements, but none are strongly expected for a list operation.

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?

A single sentence with no filler; the tool's action and output contents are specified immediately. Every phrase adds value.

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?

For a simple list operation with no output schema, the description adequately covers return content (IDs, titles, URLs, active status). Minor omissions like empty-tab-list behavior or error conditions prevent a perfect score.

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 tool has zero parameters, so the input schema carries no burden. The description correctly implies that no arguments are needed, meeting the baseline for a parameterless tool.

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 a specific verb ('List') with a clear resource ('all open browser tabs') and enumerates the returned fields (IDs, titles, URLs, active status). This clearly distinguishes it from sibling tools like browser_newTab or browser_closeTab, which modify tabs, and from browser_status, which likely reports a single tab or browser state.

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?

No guidance is given about when to use this tool over alternatives such as browser_status or browser_listSessions. The description only states what it does, leaving the agent to infer the appropriate context from the tool name and sibling set.

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