list_tabs

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

No annotations are provided, so the description carries full burden. It discloses the non-destructive nature (listing tabs) and the behavioral effect of the useProfile parameter (using cookie copies vs. clean state). However, it does not mention error conditions or the format of the returned list.

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 two sentences with no wasted words. The purpose and parameter usage are front-loaded and clearly separated.

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 description covers the operation, return fields, and parameter. Given no output schema, specifying return fields is sufficient. It could mention that the list is for the current browser context, but overall it is nearly complete for a simple list 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?

With 0% schema description coverage, the description fully explains the single parameter 'useProfile': setting it to a profile name or empty string uses a copy of real cookies/sessions, omitting it gives a clean browser. This adds essential meaning beyond the raw schema.

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 clearly states the tool lists open tabs and specifies the return fields (index, url, title, active). It distinguishes from sibling tools like open_tab, close_tab, and switch_tab by focusing on listing/reading, not modifying tabs.

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 provides guidance on when to use the useProfile parameter (for authenticated sessions vs. clean browser), but does not explicitly state when to use this tool versus alternatives like ff_list_tabs or switch_tab. The context is clear but lacks exclusionary guidance.

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