REAPER MCP Server

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

Discloses critical behavioral trait that value is normalized 0.0–1.0 and implies indices are opaque, but lacks error handling or immediate effect disclosure.

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?

Two sentences with zero fluff; purpose front-loaded and prerequisite workflow second.

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?

Complete for basic usage given no output schema exists, but could clarify relationship to set_master_fx_parameter given sibling context.

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?

Compensates for 0% schema coverage by explaining value normalization and param_index discovery, but omits semantics for track_index and fx_index.

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 verb 'Set' with clear resource 'normalized parameter value (0.0–1.0) on an FX plugin' and distinguishes workflow from siblings via get_fx_parameters reference.

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?

Provides explicit workflow guidance (use get_fx_parameters first) but lacks explicit distinction from set_master_fx_parameter sibling.

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