REAPER MCP Server

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

Discloses the render operation (side effect/cost) and explains the DR score calculation methodology (3-second blocks) beyond basic function.

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 front-loaded with action; every clause specifies behavior or output metrics with no redundancy.

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?

Lists calculated metrics compensating for lack of output schema, though return data structure/format remains unspecified.

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?

Baseline score for zero-parameter tool; no parameters to describe.

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?

Specific verbs (render, measure) and explicit metrics (RMS, peak, crest factor, DR score) clearly distinguish it from sibling analyzers like analyze_loudness or analyze_transients.

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?

Technical metrics imply usage for dynamic range assessment, but lacks explicit guidance on when to choose this over analyze_loudness or analyze_transients.

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