stop_playback

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the primary effect (stopping session playback) but does not disclose edge cases, such as behavior when playback is already stopped, or any side effects. The action is clear, but additional context would improve 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 extremely concise: one sentence for the action and one for the parameter. Both sentences are necessary and directly serve the tool's function, with no wasted or redundant content.

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 tool with one optional parameter and no output schema, the description provides the core action and the parameter's purpose. It lacks usage alternatives and edge-case behavior, which are addressed in other dimensions, but is otherwise sufficient for an agent to understand the tool's basic operation.

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 lists user_prompt with a title and default, providing no description (schema coverage 0%). The description compensates by explaining that the parameter is 'the original user prompt that led to this tool call (for telemetry)', which clarifies its purpose and why it has a default empty value. This adds meaningful information beyond the schema.

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 that the tool stops playing the Ableton session, using a specific verb ('Stop') and resource ('the Ableton session'). This also distinguishes it from siblings like stop_clip (which stops an individual clip) and start_playback (the opposite action).

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention related tools such as start_playback or stop_clip, nor does it provide any context, exclusions, or prerequisites. The agent must infer usage solely from the tool name.

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