browser.fork_session

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

With no annotations, the description must reveal behavioral traits. It describes the snapshot and creation of an independent session, implying non-destructiveness, but fails to clarify if the original session remains unaffected, or what happens if a fork fails. Lacks details on permission or resource limits.

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?

Two sentences, front-loaded with the action, no redundant words. Each sentence adds value: the first explains what the tool does, the second provides usage context.

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 3 parameters and no output schema, the description covers the main functionality but omits details about the return value (does it return a session ID?) and the optional parameters. For a tool with siblings, it partially helps differentiate but could be more 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?

Schema coverage is 0%, so the description must compensate. It mentions snapshotting 'cookies, storage state, and current URL' but does not explain the 'name' or 'start_url' parameters. The 'start_url' could override the snapshot URL, but this is not clarified, leaving ambiguity.

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's purpose: 'Fork a session' with specifics on what is snapshot (cookies, storage state, URL) and the result (new independent session). It differentiates from siblings like create_session by emphasizing state preservation, making the purpose unambiguous.

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 includes 'Useful for branching workflows or running parallel variants', which gives clear context on when to use. However, it does not explicitly state when not to use or list alternatives, such as comparing with create_session for fresh vs. cloned sessions.

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