browser_tabs

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

With no annotations, the description carries the full burden of behavioral disclosure. It states only that the tool lists tabs/targets, leaving unexplained what 'targets' means, whether sessionId is required or defaults to the active session, what the response format is, and what happens when no session is available. This is minimally transparent for a read-only listing 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?

The description is a single concise phrase with no wasted words and is front-loaded with the primary action. It earns its place, though its brevity borders on under-specification rather than economical completeness.

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, with one optional parameter and no output schema, but the description still fails to communicate essential context about sessionId semantics, return values, or how this listing relates to tab-management siblings. An agent would likely need to infer or experiment to use it correctly.

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 0%, and the description does not explain the sessionId parameter at all. 'Of a session' hints that a session identifier is relevant, but it does not clarify whether the parameter is optional, how it is formatted, or what happens if it is omitted. With no schema documentation, this is a significant gap.

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 action ('List') and a clear resource ('tabs/targets of a session'), which distinguishes it from sibling tab-manipulation tools like browser_close_tab or browser_use_tab. It does not explicitly contrast with those siblings, but 'list' and 'of a session' give a solid functional identity.

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 versus alternatives such as browser_sessions, browser_use_tab, or page_state. The phrase 'of a session' provides mild context, but there is no mention of prerequisites, when this is the preferred tool, or what differentiates it from closely related siblings.

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