Auto-Browser

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

With no annotations provided, the description carries the full burden and succeeds in disclosing what state is preserved (cookies, storage, URL) and the independence of the new session. Minor gap: does not clarify if the original session remains active or mention any limits on fork depth.

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 with zero waste: first defines the mechanism and behavioral contract, second provides usage context. Information is front-loaded with the action verb and efficiently structured.

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?

Adequate for understanding the conceptual operation, but significant gaps remain: no output schema exists (return value unexplained), and the 0% schema parameter coverage is not sufficiently compensated by the description. Missing operational details like error conditions or session lifecycle implications.

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% and the description fails to compensate adequately. While 'session_id' is implied as the source, the description provides no guidance on the 'name' parameter (presumably for the new session) or 'start_url' (likely to override the copied URL), leaving critical parameters undocumented.

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 defines the specific action (forking/snapshotting state) and resources (cookies, storage, URL) involved. It distinguishes from siblings like create_session by emphasizing the state-copying behavior ('snapshot... then create') and the 'independent' nature of the result.

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?

Provides clear context for when to use ('branching workflows', 'running parallel variants'), implicitly contrasting with create_session (fresh sessions). However, it lacks explicit 'when not to use' guidance or named alternative tools for scenarios requiring fresh sessions.

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