Create Browser Session

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

With no annotations, the description discloses isolation, no cookie leakage, pool limits, auto-expiry, and keep-alive necessity. It lacks details on error scenarios or authorization, but the behavioral traits are well covered.

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 concise 5-sentence paragraph, front-loaded with the core purpose and progressively adding details. Every sentence adds value with no redundancy.

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 (17 parameters, no output schema), the description covers essential behavioral aspects like isolation, limits, and keep-alive. It could mention error handling or pool saturation, but it is adequate for a creation tool.

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 input schema has 100% description coverage for all 17 parameters, so the baseline is 3. The description adds some high-level context (e.g., session isolation) but does not significantly enhance parameter understanding beyond the schema.

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 with its own cookies and state, distinguishing it from related tools like session_destroy or session_list. It specifies the action, resource, and key traits.

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 clear guidance on when to use the tool, including the pool limit and auto-expiry. It recommends a keep-alive pattern for long sessions, but does not explicitly contrast with session_create_batch or mention when not to use.

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