Create browser page

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

Annotations already indicate this is not read-only (readOnlyHint: false). The description adds valuable behavioral context about cookie/storage sharing with the session and advises when isolation is needed. It does not disclose all potential side effects (e.g., that a new tab might appear visibly), but it goes beyond annotations by explaining the sharing semantics, which is useful for the agent.

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 consists of two sentences with no redundancy. The first sentence gives the core action, the second provides usage context. Every word contributes to the meaning, and it is front-loaded with the essential purpose.

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 simple tool with one parameter, the description fully covers the main use case and contrasts it with an alternative. It does not detail what the created page looks like or how it behaves initially, but an output schema is present (context signal shows), which likely covers return values. The sharing/isolation guidance makes the tool's context clear enough for effective use.

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%, so the description must compensate for parameter explanation. It mentions 'explicitly addressed session,' which implies the single parameter sessionId identifies the target session, but it does not explicitly state that sessionId is the unique identifier for the session. This is implicit rather than direct, so it only partially compensates for the lack of schema documentation.

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's function: 'Create an additional page inside one explicitly addressed session.' This uses a specific verb (create) and resource (page), scoped to a session, and distinguishes it from sibling tools like browser_session_create (which creates sessions) and browser_page_close (which closes pages). The purpose is 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?

The description provides explicit usage guidance: 'Use it for another tab that must share that session's cookies and storage; use a separate session instead when identity or authentication must be isolated.' This clearly states when to use this tool versus when to use a separate session, offering a concrete alternative and exclusion condition.

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