playwright__browser_tabs

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

The description confirms the destructive and non-read-only character implied by the annotations by naming 'create' and 'close'. It adds little beyond that; select/list behavior is self-evident, and no side effects such as closing the current tab when index is omitted are described here (though the schema mentions it).

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?

One short, front-loaded sentence covers all operations without redundancy. Every word contributes.

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?

With no output schema, the 'list' action's return format is not described, which could leave an agent unable to obtain tab indices for later select/close calls. Otherwise, the schema and annotations cover the main calling requirements for this simple tool.

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%, so the description does not need to repeat parameter meanings. It adds no detail beyond the schema, leaving the baseline of 3 appropriate.

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 names a specific resource ('browser tab') and four distinct operations (list, create, close, select), matching all action enum values. This clearly distinguishes it from sibling browser tools that navigate, click, or close the whole browser.

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?

The supported operations imply when to use it: any tab-management need. However, it does not explicitly contrast with alternatives such as browser_navigate (for opening a URL in the current tab) or browser_close (for closing the browser), so the comparison must be inferred.

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