REAPER MCP Server

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

Discloses envelope visibility requirement and pan value range (-1.0 to 1.0), but omits failure behavior or units for position.

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 every sentence earning its place; front-loaded with purpose followed by constraints.

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 operation but missing critical context for position parameter (time units) and track indexing scheme.

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?

Explains pan parameter semantics well but fails to clarify track_index (0/1-based) or position (units) 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?

Clear verb ('Add') and resource ('pan automation point'), implicitly distinguishes from set_track_pan via 'automation point' terminology.

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?

States prerequisite (envelope must be visible) but lacks explicit guidance on when to use versus static pan tools or volume automation.

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