REAPER MCP Server

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

Indicates recording continues until stop_transport is called and implies track arming state change, but lacks details on file creation, overwrite behavior, or exclusive arming.

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?

Extremely concise with two sentences that earn their place: purpose first, then usage instruction; no fluff.

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?

Adequate for a simple transport command but misses what happens to recorded data (new item creation, file storage) and lacks parameter details.

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?

Implies track_index selects the track to arm via 'Arm a track', but provides no specifics on indexing scheme (0-based vs 1-based) or validation given 0% schema coverage.

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?

Clearly states it arms a track and starts recording, distinguishing from playback tools like play_project, though doesn't specify audio vs MIDI recording.

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?

Explicitly instructs to call stop_transport when done, providing clear paired usage guidance, though lacks 'when not to use' guidance.

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