Create Browser Session

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

With no annotations, the description carries the full burden. It discloses only that a session is created and that authContextId can load saved login state. It does not mention session lifecycle, resource cleanup, or any side effects, leaving behavioral transparency weak.

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 two sentences, front-loaded with the main action and a concise note on optional parameters. No wasted words.

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 create tool with no annotations, the description covers the core purpose and optional parameters but lacks richer context about session management and integration with sibling tools. The output schema likely provides return details, so this is acceptable but not fully complete.

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 description explains startUrl and authContextId, adding meaning beyond the bare schema. It does not explain headless or browserType, but these are relatively self-evident from their names and defaults. Schema coverage is 0%, so this partial compensation warrants a middle score.

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 browser session, using a specific verb and resource. It distinguishes from siblings like get_session, list_sessions, and close_session by focusing on the 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?

The description implies it is used when a new browser session is needed and mentions optional startUrl/authContextId for loading saved login state. However, it does not explicitly contrast with alternatives like load_auth_context or explain when to use this vs existing session tools.

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