browser_tabs

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

No annotations provided, but description details action outcomes: list scopes by group, new adds to group, close/select by index/targetId. Lacks mention of error cases or side effects, but overall good disclosure.

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?

Concise with clear structure: intro, action list with brief explanations, and an important note. No redundant sentences, front-loaded with key information.

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?

Covers all actions and parameters, mentions group isolation. Lacks explicit return format for 'list', but this is minor given the tool's simplicity and schema details.

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 100%, yet description adds significant value: links actions to parameters (url for new, index/targetId for close/select) and explains groupId scoping. Also notes index is relative to group when groupId set.

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 states 'Manage browser tabs' and lists actions (list, new, close, select) with clear verb-resource pairs. It distinguishes from sibling tools like browser_tab_group by mentioning tab groups.

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?

Explicit guidance: recommends tab groups for multi-user, explains behavior with/without groupId, and advises creating group first for isolation. No explicit 'when not to use', but context makes it clear.

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