stop

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

No annotations are supplied, so the description carries the disclosure burden, and it does state the effect — playback stops. It is silent on edge behavior such as whether stopping when idle is a no-op or an error, and on whether playback position is reset, but a 0-parameter command has little behavioral surface to cover.

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?

Two words, front-loaded, with zero filler. It is on the terse side — a short qualifier such as "playback in the score" would cost nothing — but nothing in it is wasted.

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?

With no parameters, no annotations, and no output schema, there is little to document, yet the description still omits whether the tool reports anything or how it interacts with whatever tool initiates playback. Completeness is acceptable for a trivial command but not thorough.

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 takes no parameters at all, so there is nothing for the description to explain beyond the schema; the baseline for a parameterless tool applies.

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?

"Stop playback" gives a specific verb plus its object, which resolves the ambiguity of the bare name "stop" — an agent can tell it halts audio playback rather than deleting notes or closing a dialog. It doesn't name any sibling to contrast with, but no sibling in the list plausibly overlaps with playback control.

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 when-to-use case (halt playback that is currently running) is only implied by the verb; there is no explicit statement of preconditions, of what happens when nothing is playing, or of which tool starts playback. For a zero-argument command the inference is easy, so this is adequate rather than deficient.

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