stop_playback

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'Stop playing' with no mention of side effects like whether recording is stopped, playhead position is reset, or if the action is idempotent. The description essentially restates the tool's name, providing minimal additional transparency.

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 short sentence, 'Stop playing the Ableton session.', that is immediately informative and contains no unnecessary words. It is perfectly front-loaded and concise.

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 simple action with no parameters, no output schema, and a clear semantics, the description is nearly complete. It could be slightly enhanced by explicitly noting that it stops the transport/global playback (as opposed to clips), which would improve differentiation from sibling tools, but overall it suffices 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?

The tool has zero parameters, so the input schema fully covers the parameter space. The description adds no parameter details, which is acceptable since there are none to document. Baseline 4 is appropriate for a no-parameter 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 uses a specific verb 'Stop' and a clear resource 'the Ableton session', clearly indicating it halts global playback. It distinguishes from sibling tools like stop_clip, stop_scene, and stop_all_clips by focusing on the session/transport rather than individual clips or scenes.

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 intended use is implied from the name and description, but there is no explicit guidance on when to prefer this over alternatives such as stop_clip or stop_all_clips. No exclusions or alternative suggestions are provided, so it relies on the user's understanding of the domain.

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