browserbase_session_create

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

No annotations are provided, so the description carries the full burden. It mentions that sessions can be created or reused and set as active, but doesn't disclose behavioral traits such as whether this requires authentication, has rate limits, what happens if a sessionId is invalid, or how long sessions persist. For a tool that likely involves resource allocation and state management, this is a significant gap.

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, efficient sentence that front-loads the key action and resource. Every word earns its place, with no wasted verbiage, making it easy to parse quickly.

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 complexity of session management (likely involving state, resources, and potential side effects), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'set as active' means in practice, what the tool returns, or any prerequisites. For a tool with such implications, more context is needed.

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%, with the schema fully documenting the optional sessionId parameter. The description adds minimal value beyond the schema by implying that sessionId is for reuse, but doesn't provide additional semantics like format examples or edge cases. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Create or reuse') and resource ('Browserbase browser session'), and specifies it will be 'set as active'. It distinguishes from siblings like 'browserbase_session_close' by being about creation rather than termination. However, it doesn't explicitly differentiate from other session-related tools if they exist beyond the listed siblings.

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 implies usage when needing a browser session, but doesn't explicitly state when to use this tool versus alternatives like 'browserbase_stagehand_navigate' or other session tools. It mentions reusing an existing session via sessionId, providing some context, but lacks clear guidance on when to create new versus reuse or when not to use this tool.

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