REAPER MCP Server

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

Discloses critical behavioral trait that values must be normalized (0.0–1.0), but lacks info on error handling, validation, or side effects.

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 single sentence with no redundancy; every word provides essential information about scope and value 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 a simple setter with flat schema, but missing guidance on parameter indexing conventions and cross-tool workflow.

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 coverage, only explains the value range (0.0–1.0) but fails to clarify fx_index/param_index semantics or their relationship to list_master_fx/get_fx_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?

Specific verb 'Set', specific resource 'master track FX plugin', and distinguishes from sibling 'set_fx_parameter' by specifying 'master track'.

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?

Implies usage through 'master track' naming but lacks explicit guidance on when to use vs regular track FX tools or alternatives.

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