browser_record_stop

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

No annotations are provided, so the description carries the burden. It discloses that the tool encodes the video and returns path, duration, size, and format, which is useful behavioral context. However, it does not mention error conditions (e.g., stopping when nothing is recording) or whether the file is written to disk, leaving gaps for a mutation/IO tool.

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 compact sentences with zero waste: the action is front-loaded and the return values follow. Every sentence earns its place.

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?

There is no output schema, but the description lists the return values (path, duration, size, format), so the agent knows what to expect. Combined with zero parameters, this is nearly complete, falling short only on error-condition behavior.

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 takes zero parameters, so there is no parameter semantics to document. The baseline of 4 applies since nothing in the schema needs compensation.

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?

States a specific verb (stops the recording, encodes the video) and explicitly ties it to sibling browser_record_start, so the agent can tell it apart from browser_teach_stop or browser_screenshot. It is clear but does not elaborate on scope beyond that pairing.

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?

Usage is implied by the reference to browser_record_start (call this to end that recording), but there is no explicit statement of when to use it, prerequisites, or what happens if no recording is active. The pairing gives more than a bare name, but no exclusions or alternatives are named.

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