multi_browserbase_stagehand_session_create

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 traits: the tool creates an isolated browser session with independent cookies, authentication, and state, and it's designed for parallel workflows. However, it lacks details on error handling, performance implications, or session lifecycle management, leaving some behavioral aspects unspecified.

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 front-loaded with the core purpose, followed by usage guidelines and behavioral details in a logical flow. Every sentence adds value without redundancy, making it efficient and well-structured for quick comprehension.

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 no annotations and no output schema, the description does a good job covering purpose, usage, and key behaviors. However, it lacks details on return values or error cases, which are important for a creation tool. The context is mostly complete but could be enhanced with output information.

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 description coverage is 100%, so the baseline is 3. The description adds value by implicitly contextualizing parameters: it mentions 'tracking multiple sessions' and 'debugging and session management' for the 'name' parameter, and 'resume an existing session' for 'browserbaseSessionID', enhancing understanding beyond the schema's technical descriptions.

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 verb ('create') and resource ('parallel browser session'), specifying it's for 'multi-session workflows' and 'multiple browser instances running simultaneously'. It distinguishes from siblings like 'browserbase_session_create' by emphasizing parallel capabilities and isolation features, making the purpose specific and differentiated.

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 explicitly states when to use this tool: 'when you need multiple browser instances running simultaneously' and lists specific use cases (e.g., parallel data scraping, A/B testing). It also provides guidance on pairing with session-specific tools and mentions alternatives implicitly by contrasting with non-parallel siblings, offering clear usage context.

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