browser_stop_recording

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

No annotations are provided, so the description carries the full burden. It discloses that the recording is stopped and frames are compiled to MP4 using FFmpeg, which implies a dependency and a destructive action. However, it does not describe what happens to the output file (e.g., where it is saved, if it's returned) or error behavior (e.g., if no active recording exists).

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 a single, well-constructed sentence that delivers the key action and outcome. It is front-loaded and contains no extraneous words, earning its place with high efficiency.

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, no annotations, and no parameters, the description is the sole source of context. It covers the core behavior but lacks details on output (return value, file location), prerequisites (active recording, FFmpeg installation), and edge cases (no active recording). This leaves gaps for a tool with no other structured information.

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 tool has zero parameters, and the schema covers 100% of them (none). The description does not need to add parameter-level meaning, and the baseline for zero parameters is 4. No additional parameter information is necessary.

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 uses a specific verb ('Stop'), identifies the resource ('the active recording'), and states the outcome ('compile the frames into an MP4 video using FFmpeg'). This clearly distinguishes it from sibling tools like browser_start_recording (starts) or browser_dump_dvr (dumps raw data).

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 implies usage when there is an active recording that needs to be finalized, but lacks explicit guidance on when to use this tool versus alternatives (e.g., browser_dump_dvr), prerequisites, or conditions under which it should not be used.

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