REAPER MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description does not explicitly confirm it is safe/non-destructive, nor does it describe error behavior (e.g., invalid indices), performance characteristics, or return data structure beyond the content types mentioned.

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?

The description is a single, efficient sentence of 12 words with the action verb front-loaded. However, given the complete lack of schema descriptions and annotations, it may be overly terse—trading necessary context for brevity.

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?

With no output schema provided, the description briefly mentions return values ('names, indices, and current values') but lacks detail on data structure (array vs object). Combined with zero schema coverage and no annotations, the description is insufficient for an agent to understand prerequisites, error handling, or return format.

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 description coverage is 0% (only titles 'Track Index' and 'Fx Index' exist). The description fails to compensate by explaining what these indices represent, their expected format (0-based vs 1-based), valid ranges, or how to obtain them (e.g., from list_tracks or list_track_fx). This is a critical gap for a tool requiring specific resource identifiers.

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 tool 'Get[s] all parameters for an FX plugin' with specific details about the return content ('names, indices, and current values'). However, it does not explicitly differentiate from sibling tool set_fx_parameter or clarify that this is a read operation versus a write operation.

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 no guidance on when to use this tool versus alternatives like list_track_fx, nor does it mention prerequisites (e.g., that fx_index must be obtained from list_track_fx first). There is no mention of when not to use it or workflow context.

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