browser.new_page

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

Without annotations, the description only says 'in the current context,' which implies an existing browser session. It does not disclose whether the new page opens in a new tab or window, or if the focus shifts to it. Minimal transparency for a simple action, but acceptable.

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?

Single sentence with no extraneous words. Perfectly concise and front-loaded.

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?

Given zero parameters and no output schema, the description is adequate. However, it could mention what the tool returns (e.g., handle to new page) or how the new page is integrated into the browsing context. The sibling tools list is dense, so added context would help.

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?

No parameters exist, so the description adds value by explaining the purpose. Baseline for 0 parameters is 4, and the description is sufficient to understand the tool's function.

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 it opens a new page/tab in the current context, distinguishing it from siblings like browser.goto (navigate existing page) or browser.close (close tab). The verb 'Open' and resource 'new page/tab' are specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives such as browser.goto or browser.launch. Sibling tools include various navigation and tab management commands, but no explicit when/when-not criteria are provided.

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