REAPER MCP Server

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

Notes that semitones can be fractional (useful behavioral detail), but omits whether changes are destructive, real-time, or require transport stop; no annotations provided to contradict.

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 sentence is appropriately terse and front-loaded with the core action, though brevity comes at the cost of missing parameter explanations.

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 a simple transformation tool but lacks critical context about the track/item addressing scheme and side effects given the DAW environment complexity.

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?

With 0% schema coverage, the description mentions 'semitones' and implies 'audio item' but fails to explain the coordinate system (track_index/item_index) or their indexing scheme.

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?

Clearly states the specific action (adjust pitch) and resource (audio item) with a key detail (fractional semitones), though it doesn't explicitly differentiate from adjust_playback_rate.

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 no guidance on when to use this versus alternatives like adjust_playback_rate or edit_audio_item, nor any exclusions or prerequisites.

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