Browser Session New

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains parameter effects (stealth, profile, proxy, etc.) but does not describe what happens after creation: whether the new session becomes active, what is returned (session ID?), or side effects on the current session. The overall behavior of the tool beyond parameter settings is undisclosed.

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 sentence followed by a bulleted list, front-loaded with the core purpose. Each parameter is given a brief, explanatory note with no extraneous words. The structure is clean and scannable, making it easy for an agent to quickly grasp the key options.

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 the tool's complexity (10 parameters, no annotations), the description is insufficient. It does not explain the lifecycle of a session—how it is activated, how it relates to other session tools (e.g., browser_session_list, browser_session_close), or that a session must exist before using navigation tools. The output schema exists, so return values are covered, but the overall workflow and prerequisites are missing.

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. It explains six parameters (stealth, profile, proxy, fingerprint, bypass_csp, record_har) with clear semantics, but leaves four parameters (name, locale, timezone, geolocation) unexplained. While these are somewhat inferable from names, the geolocation object and locale/timezone formatting are not detailed. The description adds meaningful value for most parameters but does not fully cover 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 clearly states the tool creates a new isolated browser session. The verb 'create' and the resource 'isolated browser session' are specific, and the term 'isolated' differentiates it from tab-level operations like browser_tab_new. The purpose is unambiguous and distinct from sibling tools such as browser_session_list or browser_session_close.

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 no guidance on when to create a new session versus reusing an existing one, nor does it mention any alternatives. It only lists parameters without explaining the typical workflow (e.g., that a session must be created before navigation). No exclusions or conditions are given, leaving the agent to infer usage from context.

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