REAPER MCP Server

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

Clarifies bypass means 'disable' but omits non-destructive nature, CPU usage implications, or chain position persistence given zero annotations.

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 front-loaded with verb, no redundancy, appropriate length for simple 3-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?

Covers basic functionality but misses opportunity to clarify that plugin remains instantiated (vs removal) or bypass state persistence.

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?

Compensates for 0% schema description coverage by clarifying boolean logic (bypassed=true means disabled) and mapping 'track' and 'FX' to parameters.

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?

States specific action (enable/bypass) and resource (FX plugin on track) clearly, though could better distinguish temporary bypass vs permanent removal.

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 bypass vs remove_fx, or when disabling is preferable to adjusting parameters.

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