stop_recording

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

The description clearly states that the method blocks until the WebM file is finalized, including duration and index metadata, and that the timeout parameter controls waiting. It also discloses the return value with path, size, and duration. With no annotations provided, this is strong behavioral disclosure, though timeout failure behavior is not described.

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 short, structured, and front-loaded with the main behavior before diving into parameter and return details. Every sentence adds relevant information with no redundancy or filler.

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?

The tool is simple: one optional parameter and no output or input schema beyond the timeout. The description explains what the tool does, how it behaves, what the timeout means, and what the return value contains. The only missing detail is what happens when the timeout expires—whether it raises an error, returns partial data, or still returns a summary. This is a meaningful but minor gap in an otherwise complete description.

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 input schema only provides the parameter name and default value, and schema description coverage is 0%. The description compensates by explaining that timeout is the number of seconds to wait for the auxiliary process to close the file. This is enough for an agent to know how to set it appropriately.

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 action (end current recording), a specific resource (the recording in progress), and key behavioral constraints (waits for the WebM to be complete). The function is clearly distinct from its siblings start_recording and recording_status.

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 clearly implies this is the operation to stop a recording after start_recording has begun, but it does not explicitly mention alternatives or conditions for when recording_status might be preferable. An agent can infer the correct use case, though the guidance is not explicit.

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