browser_launch

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

With no annotations, the description takes on the full burden and does well by warning that an existing browser without CDP will be closed and relaunched, a key destructive side effect. It also states it does not create an isolated profile, adding useful behavioral context. It stops short of describing return values or whether a default page is opened.

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 composed of three concise sentences, each serving a distinct purpose: stating what it launches, warning about existing browser behavior, and clarifying the profile limitation. There is no redundant or filler content.

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?

While the core purpose and a key side effect are covered, the description omits critical operational details such as parameter semantics, expected return value, and whether a new page is automatically created. Given the lack of an output schema and annotations, these gaps leave the agent under-informed for correct invocation.

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 0% and the description provides no explanation of the three parameters (browser, confirmKill, additionalFlags). The description mentions CDP and user profile but does not map these to any parameter, leaving the agent without guidance on what values to provide.

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 clearly states the tool launches a Chromium browser with CDP and the user profile, including sessions, cookies, and accounts. It also explicitly distinguishes this from an isolated profile launch, making it specific and differentiated from sibling browser tools.

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 use when you need a browser with CDP and a persistent user profile, and clarifies that it will restart an existing non-CDP browser. However, it does not name alternatives or explicitly state when not to use this tool versus siblings like browser_restart or browser_use.

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