stop

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

With no annotations, the description carries the disclosure burden and mostly meets it: it states the transport stop, optional clip stopping via song.stop_all_clips, the quantization effect, and the returned status dictionary. It does not expand on what 'adheres to global launch quantization' means in timing terms, but the main side effects are visible.

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 compact and front-loaded, with a clear Args/Returns structure. Every sentence earns its place and no boilerplate is included.

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 two-optional-boolean stop tool with an output schema, the description covers the core behavior, both parameters, and the return contract. The only mild gap, explicit alternative routing, is already reflected in usage guidance.

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%, so the description must explain both parameters, and it does: clips is tied to song.stop_all_clips, and quantized is tied to global launch quantization. The Args section adds behavioral meaning that the bare boolean schema lacks.

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 opens with a specific verb and resource: 'Stop transport playback' and clearly marks the optional Session-clip behavior. This is unmistakably distinct from sibling tools such as play and make_clip.

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 by the verb ('Stop transport playback'), but the description never explicitly says when to prefer this tool over alternatives or when not to use it. It offers no direct routing to sibling tools such as play or get_session.

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