REAPER MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify critical details: whether loading replaces the current project, prompts for save on unsaved changes, handles missing files, or returns confirmation. It only mentions the file format constraint (.rpp).

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?

The description is a single, efficient sentence with no redundant words. The key action ('Load') appears immediately, followed by the resource and parameter reference. Every element earns its place.

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 single-parameter file operation without output schema or annotations, the description covers the basic contract adequately. However, it falls short of providing necessary safety context for a potentially destructive file operation (loading typically replaces current state), which is particularly important given the lack of destructiveHint annotations.

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?

The schema has 0% description coverage (only a title). The description provides basic semantics by mapping 'project_path' to 'file path' and implying it should point to a .rpp file. However, it lacks details on absolute vs. relative paths, required extensions, or validation rules, offering only minimal compensation for the schema gap.

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 (Load), resource type (REAPER project), and file format (.rpp). It implicitly distinguishes from siblings like create_project and import_audio_file by specifying the .rpp extension and file path source, though it doesn't explicitly contrast with alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives like create_project, import_audio_file, or save_project. It lacks prerequisites (e.g., whether a project must be saved before loading another) and exclusion criteria.

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