stop_human_recording

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

The description discloses key behaviors: it 'closes the browser' and returns a detailed timeline of events. This adds significant context beyond the name, though it does not cover edge cases like idempotency or handling of non-existent recordings.

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 two sentences, front-loading the primary action and return value. Every sentence adds value without redundancy.

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 parameters and no output schema, the description adequately covers what the tool does and what it returns. It lacks prerequisites (recording must be active) but is otherwise complete for the tool's simplicity.

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?

There are no parameters, so the description does not need to add param info. Baseline 4 applies as per guidelines.

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 the active human recording session and returns a synchronized timeline. It distinguishes from siblings by focusing on 'human recording' but does not explicitly differentiate from similar tools like browser_stop_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?

The description suggests using get_session_summary and query_session_telemetry after stopping, but does not specify when to use this tool versus alternatives (e.g., browser_stop_recording) or provide exclusion criteria.

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