browser.create_session

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

With no annotations, the description should disclose behavioral traits (e.g., resource limits, idempotency, error cases). It only states it creates a session and optionally navigates, leaving critical behaviors like session lifecycle, permission requirements, and side effects 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 a single sentence, front-loaded with the main action. It is concise but could benefit from additional structure given the tool's complexity. Every word earns its place.

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 12 parameters, no output schema, and no behavioral context, the description is severely incomplete. It omits return values, error conditions, resource management, and parameter dependencies (e.g., proxy fields).

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?

Only one of 12 parameters (memory_profile) has a description in the schema, yielding 8% coverage. The tool description adds no parameter explanations, so the agent must infer from names alone, which is insufficient for parameters like 'protection_mode' or 'totp_secret'.

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 the resource 'browser session', and mentions optional navigation to a start URL. It distinguishes from siblings like 'close_session' and 'fork_session' by implying this is the initial creation action.

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 on when to use this tool vs alternatives like fork_session. No prerequisites, exclusions, or context on when creation is appropriate versus reusing an existing session.

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