REAPER MCP Server

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

With no annotations provided, the description fails to disclose critical behavioral traits: it omits side effects (e.g., impact on current project state), ignores the 'name' parameter entirely, and provides no information about return values or defaults beyond the schema.

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 concise and front-loaded with the action, but given the lack of annotations and schema descriptions, it is underspecified rather than efficiently complete. The omission of the 'name' parameter wastes the limited space available.

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?

For a destructive/lifecycle operation (creating a new project) with zero annotations and no output schema, the description is insufficient. It lacks essential context about project lifecycle management, parameter requirements, and operational side effects.

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 description coverage is 0%, requiring the description to compensate. However, it only mentions 2 of 3 parameters ('tempo' and 'time_signature') and adds no semantic context (e.g., units for tempo, format for time_signature) beyond the schema titles. The 'name' parameter is completely 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?

Clearly states the specific action ('Create') and resource ('REAPER project'). However, it does not explicitly distinguish from the sibling tool 'load_project' (which opens existing projects vs. creating new ones).

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 tool versus 'load_project' or other project lifecycle tools. Missing prerequisites such as whether this closes the current project or handles unsaved changes.

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