REAPER MCP Server

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

With no annotations provided, the description carries the full burden. It successfully discloses the soloing mechanism and file naming convention ('Files are named after the track names'), but fails to mention whether solo states are restored after rendering, file overwrite behavior, or format constraints.

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 three sentences (38 words) with minimal waste. The purpose is front-loaded in the first sentence, though the second sentence uses a colon-based structure ('track_indices: list...') that reads more like schema documentation than natural language.

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 complexity of audio rendering (5 parameters, no output schema, no annotations), the description covers the core workflow but lacks critical operational details like side effects on project state, supported audio formats, or default value explanations for the three undocumented parameters.

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%, requiring the description to compensate. It documents track_indices explicitly and implies output_directory usage, but completely omits format, sample_rate, and bit_depth parameters, leaving 3 of 5 parameters undocumented.

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 clearly states the specific action ('Render each track as a separate stem file') and mechanism ('by soloing each track individually'), distinguishing it from sibling tools like render_project or render_time_selection that lack the per-track soloing approach.

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?

While the description explains the track_indices parameter ('list of track indices, or null to render all tracks'), it does not explicitly compare this tool to render_project or render_time_selection to guide when to use stems versus full mix or time-selection rendering.

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