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. It successfully discloses the default save location (~/Documents/REAPER Projects), but omits critical behavioral details like overwrite behavior, whether it creates parent directories, error conditions for invalid paths, or that this is a destructive write operation.

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?

Two sentences with zero waste: first states the action, second provides the default behavior. Information is front-loaded and appropriately sized for a single-parameter tool.

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 save operation, but given this is a file I/O tool with no output schema, it should mention overwrite behavior or file format (.rpp). The description meets minimum needs but leaves operational safety questions unanswered.

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 description coverage, the description effectively compensates by explaining the parameter's purpose through context ('If no path is given'), implying project_path is an optional file path. It clarifies the default behavior when the parameter is empty, adding necessary semantic meaning absent from the 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?

The description clearly states the core action ('Save the current project') with specific verb and resource. However, it doesn't explicitly distinguish from siblings like create_project or load_project, which could confuse an agent about whether the project must already exist.

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 implicit guidance through the default path behavior ('If no path is given...'), explaining what happens when the parameter is omitted. However, it lacks explicit when-to-use guidance comparing it to create_project or load_project, and doesn't mention prerequisites (e.g., whether a project must be created first).

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