browser_begin_handoff

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

No annotations provided, but description fully discloses behavior: records human actions with provenance, captures flight recorder data, enables subsequent timeline tools. Also mentions requirement for visible session and completion methods.

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?

Description is somewhat lengthy but well-organized with clear sections. All sentences add value. Could be slightly more concise but front-loads purpose effectively.

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 no output schema and a simple parameter, the description fully covers the handoff process, what happens to human actions, and how to end the handoff. No missing context for an agent to use this tool correctly.

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 100% for the single 'note' parameter. Description does not add meaning beyond schema; it only restates that the note is recorded on the timeline. Baseline 3 is appropriate.

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?

Explicitly states 'HUMAN HANDOFF' and describes pausing agent automation to let a human reproduce behavior. Differentiates from sibling tools like browser_end_handoff by framing the start of the handoff workflow.

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 (agent cannot reproduce behavior) and steps to follow after calling. Does not explicitly exclude alternative tools but implies this is for failure recovery.

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