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 disclosure burden. It usefully implies the file is finalized and its path returned, but it does not say whether the output file is retained afterward, what happens on an idle recorder, or what the returned `output` looks like if encoding is still in flight.

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?

A single front-loaded sentence with the action and its result; no filler, no redundancy. Nothing could be cut without losing information.

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?

For a zero-parameter, single-purpose tool with an output schema, the description covers the essentials, and the output schema handles the return shape so it need not be elaborated. The only real gap is the lack of differentiation from sibling stop/cancel/pause operations.

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 nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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 gives a specific verb and resource ("Stop the running recording") plus the side effect (returns the final MP4 path). It is clear in isolation, but it does not distinguish itself from the closely related siblings cancel_recording and pause_recording, which an agent will need to choose between.

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 phrase "the running recording" implies a prerequisite state (a recording must be active), which is useful implied guidance. However, there is no explicit statement of when to choose this over pause_recording or cancel_recording, and no note about what happens if nothing is recording.

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