list_all_tabs

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that chrome-extension:// pages never become sessions because content scripts cannot run there, that those tabs have no session id, and that the tool works even with no tabs open. These are meaningful behavioral details beyond a simple 'list' operation, though it does not discuss return structure, which is partially covered by the output schema.

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 compact, front-loaded with the core purpose, and every sentence earns its place. It states the main action, then adds the critical exception and the alternative tool, and closes with an edge-case guarantee. There is no redundant or filler language.

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 list tool with an output schema, the description covers the important edge cases: extension pages are included, they lack session ids, and cdp_command is the correct driver for them. It also handles the empty-tabs case. The main completeness gap is the unexplained session_id parameter, but the tool has no required parameters and a default null, so the core invocation path remains clear.

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 schema has one optional parameter, session_id, with 0% schema description coverage, so the description should explain it. The description mentions the concept of session ids but never explains what the session_id input parameter does or how it affects the call. An agent gets no parameter guidance beyond the schema's bare type/default information.

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 and resource: 'List every open tab', and immediately distinguishes itself from the sibling tool list_tabs by noting it includes chrome-extension:// pages that list_tabs hides. This makes the tool's scope unmistakable and differentiates it from its closest sibling.

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 explicitly names list_tabs as the sibling that hides extension pages, making it clear when list_all_tabs is the more comprehensive choice. It also gives a concrete alternative for extension pages that have no session id: drive them with cdp_command(tab_id=...) instead. This is explicit when/alternative guidance.

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