Render a REAPER project and measure its dynamic range—RMS, peak, crest factor, and a 3-second-block DR score—to assess loudness and mix dynamics.
Render the project and measure dynamic range: RMS, peak, crest factor, and a simplified DR score (average peak-to-RMS over 3-second blocks).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose two important things: the tool renders the project (an expensive, potentially side-effecting operation) and the exact DR algorithm used ('average peak-to-RMS over 3-second blocks'). It omits whether the render is written to disk or discarded, whether it requires stopped transport, and roughly what cost/runtime to expect.
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?
A single tight sentence with the action front-loaded and the metric list following immediately. Every clause is informative – even the parenthetical definition of the DR score earns its place by pinning down a metric that varies between implementations.
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?
For a zero-parameter analysis tool with no output schema, the description usefully implies what comes back by naming RMS, peak, crest factor, and DR. It still leaves the rendering side effect unexplained and gives no basis for choosing this over analyze_loudness, which is the main ambiguity an agent faces here.
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?
The schema has zero parameters, so there is nothing for the description to compensate for. The enumerated metrics describe measurements rather than inputs, meaning no parameter meaning is left ambiguous.
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 a specific verb and resource ('Render the project and measure dynamic range') and enumerates the exact metrics produced, which is far more informative than a generic 'analyze' label. It does not, however, distinguish itself from the closely related analyze_loudness or detect_clipping siblings, which an agent will have to disambiguate on its own.
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 this tool should be chosen over analyze_loudness, analyze_frequency_spectrum, analyze_transients, or detect_clipping, all of which live in the same sibling set. Usage must be inferred from the metric list alone, and there are no stated preconditions (project loaded, transport stopped) despite the tool rendering.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.