browser_new_page

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

With no annotations, the description carries the disclosure burden. It does mention that the new tab becomes active and that a URL can be optionally navigated to, but it omits side effects such as whether it waits for page load, failure behavior on invalid URLs, or how the new page is referenced afterward.

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 short, front-loaded sentences contain no filler. The core action ('Open a new page/tab and make it active') comes first, followed by the optional behavior in a separate sentence.

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 tool with one optional parameter and no output schema, the description is reasonably complete. But it could go further: it doesn't describe what happens if the browser isn't running, whether the tool returns a page handle, or how loading errors are surfaced. These details matter given the rich sibling set around page management.

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?

Although schema description coverage is 0%, the description's phrase 'Optionally navigate to a URL' directly explains the single `url` parameter's purpose and optionality. The one parameter is effectively covered, adding meaning beyond the bare schema.

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 verb ('Open'), a concrete resource ('new page/tab'), and a clear behavioral outcome ('make it active'). It distinguishes itself from sibling tools like browser_navigate by emphasizing 'new page/tab' rather than navigating in the current page.

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 usage context is implied: you would use this when you need a new tab/page and want it to be active. However, it doesn't explicitly mention when not to use it or name alternatives like browser_navigate or browser_switch_page, leaving some routing to inference.

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