browser_open

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

With no annotations provided, the description carries the full burden. It does disclose that a browser is opened, navigated, and reused, but it omits important behavior such as whether an existing session is replaced, what happens if the browser cannot open, or the effect of the default headless mode.

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?

The description is a single, front-loaded sentence with no filler words. It conveys the main action and the shared-session behavior efficiently, though it is terse enough to leave semantic gaps.

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 browser-control tool with no annotations and minimal parameter coverage, the description is incomplete. It covers the overall purpose and the shared browser trait, but an agent would still lack guidance on headless behavior, session lifecycle, and how this operation relates to the browser_start/browser_connect siblings.

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 0%, and the description does not add meaning for either parameter. 'url' is only implied by 'navigate to target page', and 'headless' is not mentioned at all.

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 a specific action ('open Playwright browser') and resource ('target page'), and adds the shared-browser behavior. It is clear, but it does not explicitly differentiate from sibling tools like browser_start or browser_connect.

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 description implies that the browser is reused by subsequent tools, but it gives no explicit guidance on when to choose this tool over alternatives such as browser_start or browser_connect. There are no exclusion conditions or when-not-to-use hints.

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