live_list_tabs

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

With no annotations provided, the description carries the full burden of disclosure. It explains the output includes tab id, title, url, active status, and the pinned target, which is valuable behavioral context. It does not mention side effects (likely none for a list operation), auth, or rate limits, but it conveys the essential behavior accurately.

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 sentence that front-loads the primary action and enumerates the returned fields. It includes a direct usage note without unnecessary verbosity, earning a top score for structure.

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?

Given no output schema, the description sufficiently explains the return values (id, title, url, active, pinned). It also provides context about the pinned target and the prerequisite for live_switch_tab. For a read-only list tool, this is comprehensive.

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 covers both parameters (project and session) with descriptive text, so schema coverage is 100%. The description adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 verb 'lists' and the resource 'every open tab in the side panel's browser window', enumerating the exact fields returned (id, title, url, active, pinned). It distinguishes itself from sibling tools like live_switch_tab (which switches) and live_new_tab (which creates) by focusing on enumeration.

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 instructs 'Call this before live_switch_tab to get a valid tabId', giving a clear when-to-use directive. It does not explicitly state when not to use it, but the context is sufficient for an agent to understand its purpose relative to the sibling live_* tools.

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