sonic_stop_recording

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

With no annotations provided, the description carries the full burden of disclosing side effects. It only says 'Stop' without explaining what happens to the recorded audio, whether the recording is saved, or if stopping when not recording causes an error. This is minimal behavioral disclosure.

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 a single sentence with no filler or redundant content. It is front-loaded and appropriately sized for a simple stop operation, although it lacks detail elsewhere.

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?

Despite the tool's simplicity, the description is incomplete: it omits any explanation of the `collect_ms` parameter, the effects of stopping, and the expected behavior when the recorder is not running. The presence of an output schema reduces the need to describe return values, but the parameter gap remains significant.

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 sole parameter `collect_ms` has 0% schema description coverage, and the description does not add any meaning. The name hints at a time-based behavior, but it is not explained, leaving the agent to guess what value to supply.

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 action ('Stop') and the specific resource ('Sonic Pi's built-in WAV recorder'), distinguishing it from the sibling tool `sonic_stop` which would be a generic stop. It is specific and unambiguous.

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?

No explicit guidance is provided about when to use this tool versus alternatives. It is implied that it pairs with `sonic_start_recording`, but there is no mention of prerequisites, sequencing, or cases where another stop tool might be more appropriate.

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