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. It discloses the basic read-only nature and output format (titles/references), but omits behavioral details like permission requirements, privacy considerations, or whether tab references are persistent IDs.

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?

Single sentence, front-loaded with the action verb, and zero wasted words. Every component earns its place by defining scope ('all open tabs'), location ('user's browser'), and output ('titles and tab references').

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 simple single-parameter tool without output schema, the description adequately explains what the tool returns. It could be improved by mentioning the URL inclusion option described in the schema, but it covers the core functionality sufficiently.

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?

Schema description coverage is 100%, establishing a baseline of 3. The description does not mention the includeUrl parameter or its default behavior (URLs excluded), leaving all parameter semantics to the schema itself.

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 ('List') and resource ('open tabs'), and distinguishes from siblings by specifying it returns 'titles and tab references' (metadata) rather than content, clearly differentiating it from read_tab_content.

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?

While the description implies usage by stating it returns tab references (suggesting it's for discovery before reading), it lacks explicit guidance on when to use this versus read_tab_content or workflows like 'use this first to get tab IDs'.

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