list_tabs

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

With no annotations, the description carries the full burden. It does disclose the output convention that the active tab is marked with *, which is genuinely useful behavioral detail, but it says nothing about window scoping, ordering, permissions, or whether it reflects live browser state.

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?

Two short sentences, zero waste, and the output-marker detail is front-loaded right after the core action. Nothing is padded.

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?

There is no output schema, so the description should carry the return-value burden. It partly does (ids plus active marker), but leaves unclear whether tabs are scoped per window, their ordering, and what identifying context beyond an id is returned.

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 zero parameters and 100% coverage, so the baseline of 4 applies. There are no arguments for the description to explain.

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?

States a specific verb+resource (list open tabs) and even describes the output shape (ids, active marked with *). However, it offers no differentiation from siblings like get_text or read_page, which also surface page content, so an agent must infer when a tab listing is the right call.

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 when-to-use or when-not guidance, and no mention of the obvious companion tools (switch_tab, close_tab, new_tab). Usage is only implied — the agent must infer it should call this before switching or closing a tab.

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