stop_recording

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It only states 'Stop recording' without revealing whether it affects session or arrangement recording, whether it is safe to call when not recording, or what side effects occur (e.g., saving, discarding).

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, brief sentence that conveys the core action with no wasted words. It is appropriately front-loaded and earns its place.

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?

Even for a zero-parameter tool, the description is too thin. It fails to provide essential context about recording scope (session vs arrangement), behavior when no recording is active, and relationship to sibling recording controls. The absence of an output schema increases the need for such explanatory detail.

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 has zero parameters, so the schema is complete and the description need not add parameter-level detail. The baseline of 4 applies because no parameter information is required.

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 'Stop recording in Ableton.' clearly uses the verb 'stop' with the resource 'recording', making the primary action unambiguous. It does not, however, distinguish among recording types (session vs arrangement) or compare to sibling tools like toggle_session_record, so it lacks sibling differentiation.

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 usage guidance is provided. The description gives no indication of when to use this tool versus alternatives such as stop_playback, toggle_session_record, or toggle_arrangement_record, nor any exclusions or prerequisites.

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