browser_stop_recording

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

Discloses format inference, fps constraints, and also_gif behavior. No annotations provided, so description covers basic safety. Lacks details on file overwriting or side effects.

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?

Concise with main action upfront. Some verbosity in example, but still readable and efficient.

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?

Description covers most parameters but omits session_id. Output schema exists, reducing need for return value docs. Adequate but not fully complete.

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?

Explains path extension, fps, and also_gif. Missing any explanation for session_id, which is not mentioned despite schema coverage 0%. Partial coverage.

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 the tool stops recording, encodes video, and returns file path. It differentiates from sibling browser_start_recording by specifying the end of recording.

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 context for format inference, fps, and also_gif, giving a practical use case for GitHub. Could explicitly contrast with start or other recording tools, but context is sufficient.

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