stop

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

Annotations only indicate destructiveHint=false, so the description carries the burden of explaining the tool's effect. It states the behavior plainly: playback is stopped. It does not add additional context such as whether the edit cursor moves, whether playback position resets, or whether an already-stopped transport is a no-op.

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 a single, direct sentence with no filler or redundancy. It is appropriately minimal for a no-argument transport control.

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, zero-parameter transport command, the description is nearly sufficient. The main gap is the lack of any distinction from 'pause', which is a closely related sibling, but the tool's simplicity and empty schema keep the completeness high.

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 has zero parameters, so there are no parameter semantics to clarify. The schema coverage is 100% and no parameter documentation is needed.

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 ('Stop') and resource ('playback'), making the core action clear. It is easily distinguished from most siblings by name and behavior, though it does not explicitly contrast with the sibling 'pause'.

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 implies the tool is used when the agent needs to halt playback in REAPER. However, it provides no explicit guidance on when to choose 'stop' over the closely related sibling tools 'pause' or 'record'.

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