REAPER MCP Server

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

Lacks critical behavioral details: does not clarify if deletion removes underlying media/items, whether index is 0 or 1-based, or if operation is undoable.

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 terse (6 words) and front-loaded, but insufficiently detailed for a destructive operation; misses safety warnings that should earn their 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?

Incomplete for a destructive operation; fails to explain side effects on track contents, relationships to buses/sends, or return behavior despite having no output schema.

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 that track_index identifies which track to delete, though omits index basis (0 vs 1).

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 (delete) and target (track by index) but does not differentiate from sibling removal tools like remove_fx or remove_send.

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?

Provides no guidance on prerequisites (e.g., obtaining index via list_tracks), data loss warnings, or when to prefer this over muting/soloing.

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