REAPER MCP Server

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

Discloses insertion point ('at the end of the project') but lacks information on return values, error conditions, or naming constraints despite no annotations.

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 no extraneous text; critical information (location, type options) presented immediately.

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 2-parameter tool but omits semantic distinctions between track types (e.g., instrument vs midi) and lacks output guidance.

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 effectively for 0% schema coverage by enumerating valid track_type values (audio, midi, instrument, folder) not defined in the string schema.

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?

States specific action (Create) and resource (track) with location detail (end of project), clearly distinguishing from create_project/create_midi_item siblings, though create_bus ambiguity remains.

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?

Lists track_type options but provides no guidance on when to use audio vs instrument vs folder, or when to prefer create_bus over create_track.

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