Browserbase MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it creates or reuses sessions based on sessionId parameter, initializes Stagehand with configuration flags (proxies, stealth, viewport, cookies), and updates the active session. The WARNING about single-browser-only usage is particularly valuable behavioral context.

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 efficiently structured with zero waste. The first sentence establishes the core purpose, the second provides critical warnings and alternatives, and the third adds implementation details. Every sentence earns its place and the warning is appropriately front-loaded for immediate visibility.

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 (session management with Stagehand initialization) and no annotations or output schema, the description does well at covering key aspects: purpose, usage constraints, behavioral traits, and parameter implications. It could benefit from mentioning what 'updates the active session' means operationally, but overall provides substantial context for a tool with significant behavioral implications.

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?

The schema description coverage is 100% (the single parameter 'sessionId' is fully documented in the schema). The description adds some context by mentioning 'If not provided or invalid, a new session is created,' which reinforces the schema's documentation. However, it doesn't provide significant additional parameter semantics beyond what the schema already covers.

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 specific action ('Create or reuse a single cloud browser session') with the resource ('Browserbase with fully initialized Stagehand'). It explicitly distinguishes this tool from its sibling 'multi_browserbase_stagehand_session_create' by emphasizing it's for SINGLE browser workflows only, providing clear differentiation.

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 guidance on when to use this tool ('for SINGLE browser workflows only') and when not to use it ('If you need multiple browser sessions running simultaneously... use 'multi_browserbase_stagehand_session_create' instead'). It names the specific alternative tool and describes the appropriate context for each.

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