browser_start_recording

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

Discloses key behaviors: starts background recording, auto-stops after 5 minutes of inactivity, and interaction with browser_launch's autoTrackHistory. No annotations provided, so description carries the burden; additional details would improve transparency.

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?

Extremely concise: two sentences plus a note about autoTrackHistory. Front-loads the main purpose without unnecessary detail.

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?

Covers the essential aspects of recording start, auto-stop, and implicit recording interaction. Lacks details on output format, performance impact, or how to retrieve the compiled video, but these may be covered by sibling tools.

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?

Only one optional parameter (outputDir) with schema description already covering its purpose and default. The tool description adds no extra parameter context beyond what the schema provides, meeting baseline expectations.

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?

Description clearly states the tool starts recording screencast frames to compile a video, with specific details on auto-stop and finalization via browser_stop_recording, distinguishing it from sibling tools.

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?

Describes when to use (start recording) and notes the interaction with autoTrackHistory, providing clear context for usage, though it does not explicitly exclude alternatives like stream_screencast.

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