browser_tabs

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

No annotations are provided, so the description carries the full burden. It usefully discloses batch semantics (max 20, per-tab outcomes, one bad id does not strand the rest), but stays silent on whether 'close' is destructive/reversible, how 'sleep' differs in effect, and what permissions are needed.

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 dense sentences, front-loaded with the three actions, with the batch constraint and failure-isolation behavior stated compactly. No filler.

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 mutation-capable tool with no annotations and no output schema, the description covers purpose and batch behavior but omits action-specific requirements (whether 'list' ignores tab_id) and the effect/risk profile of close vs sleep.

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 coverage is only 33% (tab_id has no description), yet the description compensates by mapping tab_id to one tab and tab_ids to several, and adds the non-schema 20-item cap. It does not clarify why tab_id is required even for 'list', which leaves a small gap.

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 specific verbs (list/close/sleep) against a specific resource (workspace tabs), matching the action enum exactly. An agent can distinguish this from browser_open, browser_act, or browser_observe without opening the schema.

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?

Usage is only implied by the action verbs; there is no guidance on when to choose 'sleep' over 'close', nor when to prefer this tool over browser_open/browser_observe for tab state. Adequate but gaps remain for an agent deciding between actions.

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