pause

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

The annotation only includes destructiveHint=false, which is minimal. The description states the action but does not describe side effects, such as whether the cursor position remains, whether it affects recording, or if it resumes from the same point. There is no contradiction with annotations, but the description adds little beyond the basic action.

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 extremely concise, using a single sentence with no filler. It is front-loaded with the action and resource. Every word earns its place, making it highly scannable and efficient for an agent.

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?

Given the simplicity of the tool (no params, no output schema, no complex behavior), the description is nearly complete for its purpose. However, it lacks any mention of the relationship to playback state or potential differences from 'stop', which are relevant given the sibling tools. It is adequate but leaves a small gap for an agent unfamiliar with DAW semantics.

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 no parameters, and the schema coverage is 100% (vacuously true). Since there are no parameters to explain, the description does not need to add parameter semantics. The baseline for zero parameters is 4, and the description does not need to compensate for any undocumented parameters.

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 is very short: 'Pause playback in REAPER.' It clearly states the action (pause) and the resource (playback), which is specific enough to distinguish from sibling tools like 'play' and 'stop'. It is less detailed than a fuller description but still conveys the primary purpose without ambiguity.

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?

There is no guidance on when to use this tool versus alternatives like 'stop' or 'play'. While the name and description suggest it pauses transport, it does not clarify the difference between pausing and stopping, which could confuse an agent deciding between 'pause', 'stop', and 'toggle_repeat'. No explicit 'when not to use' guidance is provided.

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