REAPER MCP Server

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

With no annotations, the description provides the valid range (-150 to +12 dB) which is crucial behavioral context. However, it omits whether this overwrites existing automation, clamps values outside range, or throws errors.

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: first establishes purpose, second provides range constraints. Every word earns its place with zero 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?

Adequate for basic invocation but incomplete regarding DAW-specific context: interaction with volume automation, behavior when track_index is invalid, and clarification of the 'roughly' qualifier in the range specification.

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 coverage is 0%, so description carries full burden. It provides critical range constraints for volume_db and implies track targeting. However, track_index semantics (0-indexed vs 1-indexed) remain 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 (Set) and resource (track volume in dB), distinguishing it from siblings like set_master_volume and set_send_volume by explicitly specifying 'track' scope.

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?

No guidance provided on when to use this static volume tool versus set_volume_automation (which exists in siblings), or prerequisites like track existence. No alternatives or exclusions mentioned.

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