REAPER MCP Server

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

Strong disclosure of temp file creation (critical side effect) and measurement standards. Without annotations, carries burden well but misses details: temp file cleanup behavior, whether project cursor/selection is modified, and exact return format (though it names the metrics LUFS/dBTP).

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?

Single dense sentence with zero waste. Front-loaded with action (Render... and measure...), specifies metrics in parentheses, and cites standard. Every clause adds unique information.

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 parameterless analysis tool, adequately complete. Mentions temp file side effect and specific metrics measured. Without output schema, could clarify if values are returned directly or stored, but naming the metrics (LUFS, dBTP) provides sufficient expectation.

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?

Input schema has zero parameters. Description appropriately focuses on behavioral explanation rather than parameters. Baseline 4 applies since no parameter documentation is required.

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?

Excellent specificity: states the exact action (measure integrated loudness/true peak), the resource (project), the methodology (ITU-R BS.1770), and the side effect (temp file render). Clearly distinguishes from siblings like analyze_dynamics by specifying full project render and specific loudness standards.

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?

Implies usage context through 'temp file' (suggesting quick analysis without permanent export), but lacks explicit when-to-use guidance versus sibling analysis tools (analyze_dynamics, analyze_transients) or versus render_project. No mention of prerequisites like project existence.

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