list_tabs

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

With no annotations, the description carries the full burden. It clearly signals a read-only listing operation, scopes the behavior to 'all connected browsers,' and adds valuable downstream context by saying the session id should be 'passed verbatim.' It does not discuss auth or edge cases, but the core behavior is transparent for a simple list tool.

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?

One sentence front-loads the action and scope, then provides the two most operationally important output details: the browser field and the session id usage. No filler or redundancy.

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 zero-parameter list operation with an output schema, the description is essentially complete: it names scope and follow-up usage. The only notable gap is the unresolved ambiguity with list_all_tabs, but the tool call itself is fully specified.

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 there are no parameter meanings for the description to clarify. The description still adds useful context about the output fields, exceeding the baseline required for a no-parameter 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 states a specific action ('List') and resource ('connected tabs across all connected browsers'), and describes key output fields. However, it does not differentiate this tool from the similarly named sibling list_all_tabs, so it stops short of full sibling clarity.

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?

Usage is implied: the tool is for listing tabs and obtaining session IDs to pass verbatim to other tools. There is no explicit when-to-use or when-not-to-use guidance, and no comparison with the alternative list_all_tabs.

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