stop_playback

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: not what state the session is left in, whether playback position is retained, or whether it requires Ableton to be focused and connected. For a transport mutation, that context is missing.

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 definition is two short blocks with the action front-loaded and the parameter listed separately. Nothing is padded, though the 'Parameters:' heading is slightly formal for a single telemetry field.

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?

The tool is simple, an output schema exists so return values needn't be explained, and the one parameter is documented. What's missing is the piece an agent most needs in a dense transport/clip toolset: how this relates to stop_clip and set_transport. That gap keeps it at minimum-viable rather than complete.

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?

Schema description coverage is 0%, but the description explicitly documents the single param, user_prompt, as 'the original user prompt that led to this tool call (for telemetry).' That adds real meaning beyond the bare string/default field in the schema and tells the agent the value is instrumentation, not functional input.

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 states a specific verb and resource: 'Stop playing the Ableton session.' That is clear, but the tool list contains close alternatives including stop_clip, set_transport, and start_playback. The description never says how this call differs from stopping a single clip or setting transport state, so sibling differentiation is left to the agent.

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 description gives no when-to-use guidance and no exclusions. It does not say whether the tool is appropriate for halting a single clip, for the whole transport, or both, and it does not point to start_playback as the counterpart or stop_clip as the narrower alternative.

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