start

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

Without annotations, the description carries the full burden. It mentions 'create or reuse' but does not explain the behavior in detail (e.g., what happens on multiple calls, side effects, or lifecycle). The description is too shallow for a tool that manages a session.

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 extremely concise—just five words. It front-loads the core purpose. However, it could be slightly more descriptive without added length, e.g., mentioning that it initializes a new session or resumes an existing one.

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 tool with no parameters and no output schema, the description is minimally viable. It explains the basic function but lacks context on session lifecycle, error handling, or implications of 'reuse.' More detail would improve completeness.

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?

There are no parameters, so the description does not need to add parameter semantics. Per the rules, zero parameters warrant a baseline of 4. The description is sufficient for this context.

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 that the tool creates or reuses a Browserbase session. It distinguishes itself from sibling tools (act, end, etc.) which are actions within a session. However, it does not explain what 'Browserbase' is or what a session entails, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. It is implied that you use it before other session-dependent actions, but there is no explicit when/when-not/alternatives statement.

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