REAPER MCP Server

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

Provides valuable domain context (channel 9 for drums, middle C reference, relative timing) not present in schema, but omits side effects and error behaviors.

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?

Perfectly concise with clear front-loading; every line delivers essential musical parameter semantics without 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 usage but incomplete given the lack of schema descriptions for track/item indices and velocity; no output schema exists to document.

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?

Excellent semantic detail for pitch, timing, and channel, but fails to explain track_index, item_index, or velocity despite 0% schema description coverage.

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 (Add) and target (MIDI note to existing item), distinguishing it from sibling 'create_midi_item'.

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 prerequisite (existing MIDI item) but provides no explicit when/when-not guidance or comparison to alternatives like 'create_drum_pattern'.

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