Start Session

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., creating a resource), whether starting a session might fail if one already exists, authentication requirements, or any destructive potential. The description is essentially a tautology of the tool name with no added behavioral context.

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 and is concise, but it is under-specified rather than appropriately concise. It lacks critical information and does not front-load usage constraints or prerequisites. Every word earns its place, but there are too few words to be useful.

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 tool has two parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain what happens after starting a session, how to identify the session for subsequent browser_* calls, or how the provider selection affects behavior. An agent would be unable to correctly invoke this tool with confidence.

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 0%, so the description must explain the parameters. It does not mention 'provider' or 'sessionName' at all. The provider enum values (browserbase, anchor, playwright, cloudflare) are left for the schema to define, but the description should clarify their meaning or expectations, which it fails to do.

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 starts a browser session, with a specific verb and resource. It is distinct from sibling tools that operate within a session, but it does not explicitly differentiate itself from potential alternatives like 'get_sessions' or 'close_session' by noting that it is the entry point. The phrase 'using the configured provider' adds some context but is vague.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that a session must be started before using browser_* tools, nor does it mention any prerequisites such as configuration being set. The description simply states what it does without any conditional or comparative context.

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