start_human_recording

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

The description discloses that it closes existing browser sessions, opens a new headful instance, and that the Black Box flight recorder captures all interactions. With no annotations available, this fully informs the agent of behavioral traits.

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 well-structured with a bold lead sentence and a numbered workflow. Every sentence adds value, though it is somewhat lengthy; it could be slightly more concise.

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?

Despite lacking an output schema, the description fully explains the tool's purpose, workflow, and side effects. It covers all necessary context for an agent to decide when and how to use it.

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 only parameter 'url' is described in the schema as 'URL to navigate to when the browser opens'. The tool description adds no additional semantic value beyond that, and schema coverage is 100%, so 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?

The description clearly states 'HUMAN DEVELOPER TAKEOVER' and explains it pauses automation to open a visible browser for human interaction. This distinguishes it from sibling tools like browser_launch or browser_new_tab.

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 provides a step-by-step workflow (1-4) and notes it closes any existing session. However, it does not explicitly mention when not to use it or compare to alternatives among siblings.

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