tab_list

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool lists tabs with certain fields, but omits details like behavior when no tabs are open (likely empty list), potential for large lists, or whether the output is sorted. As a read operation, it is non-destructive but this is not explicitly stated.

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 efficiently communicates the tool's function and output. It is front-loaded with the action 'List all open tabs' and specifies exact fields returned. No extraneous words.

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 the tool's simplicity (no parameters, output schema exists), the description is mostly complete. It specifies what is listed and the fields returned. However, it lacks context on ordering, whether the list includes all browser tabs or just the current window, and how the 'current' flag works. Still, it covers the essential information.

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 tool has zero parameters, so schema description coverage is 100% trivially. The description does not need to add parameter details. Baseline for zero parameters is 4, and the description adds no unnecessary 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 clearly states the tool's purpose: listing all open tabs with specific details (tab_id, title, URL, current flag). It uses specific verb 'List' and distinguishes the resource 'open tabs'. It differentiates from siblings like tab_find (single tab lookup) and tab_info (specific tab details).

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for obtaining an overview of all open tabs, but does not mention when not to use it (e.g., for a specific tab, use tab_find or tab_info) or provide context about prerequisites or limitations.

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