REAPER MCP Server

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

Without annotations, the description carries full disclosure burden. It successfully documents the value range semantics (-1.0 left to 1.0 right), but fails to mention side effects (overwrites existing automation?), error conditions, or whether changes are immediate/persistent.

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 efficient: action stated immediately, followed by essential numeric range reference. No redundant words; the value mapping is critical for correct invocation and 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?

Adequate for a simple 2-parameter setter with no output schema. However, lacks confirmation of success behavior, error handling, or interaction with existing track state (e.g., current pan value).

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 has 0% description coverage. The description compensates partially by explaining the 'pan' value range, but provides no guidance on 'track_index' (e.g., zero-based vs one-based indexing, valid ranges).

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 action ('Set') and resource ('track pan'). The numeric range (-1.0 to 1.0) clarifies this controls stereo positioning, distinguishing it from sibling tools like set_track_volume or add_pan_automation (which implies dynamic vs static).

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?

No guidance on when to use this versus alternatives like add_pan_automation for automated panning. No mention of prerequisites (e.g., track must exist) or when not to use (e.g., during playback vs stopped).

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