live12_transport_stop

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

With no annotations, the description carries the full behavioral burden and falls short: it does not say whether playback stops immediately or is quantized, whether the position resets to the start, whether all playing clips are halted, or what the tool returns. The LOM reference adds a little traceability but no operational context.

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?

A single front-loaded sentence with no filler; the purpose is stated first and the implementation reference is parenthetical, so every word 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?

For a zero-parameter, no-output tool this is minimally sufficient to invoke, but because there are no annotations the description should have closed the gaps around stop timing, position reset, and clip behavior to be fully 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?

There are zero parameters, so parameter semantics default to a baseline of 4; the schema is trivially complete and the description does not need to explain any inputs.

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?

States a specific verb and resource — stopping song playback in Ableton Live 12 — and cites the underlying LOM call (Song.stop_playing). It implicitly distinguishes itself from live12_transport_play and live12_clip_stop by scoping to song-level playback, but never names those siblings explicitly.

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 use case (halt playback) is implied clearly enough for an agent to select it, but there is no explicit guidance on when to prefer it over clip_stop or other transport tools, and no prerequisites or state requirements are stated.

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