Render the project to a temporary file and measure integrated loudness (LUFS) and true peak (dBTP) per ITU-R BS.1770 to verify mix levels.
Render the project to a temp file and measure integrated loudness (LUFS) and true peak (dBTP) using the ITU-R BS.1770 standard.
| 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 usefully discloses that the tool renders the project to a temp file before measuring, which is a significant hidden side effect. However, it does not state whether the project is modified, how the temp file is cleaned up, permissions, performance, or what is returned.
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 front-loaded sentence that wastes no words. It delivers the key operation, units, and standard immediately.
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 simple no-parameter analysis tool, the description covers the essential operation, measurement basis, and temp-render behavior. It would be stronger if it explicitly described the return values or temp-file lifecycle, especially since there is 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?
The tool takes zero parameters, so there are no parameter semantics to explain. Per the baseline rule for zero-parameter tools, a score of 4 is appropriate.
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 states a specific verb and resource: render the project and measure integrated loudness and true peak. It names exact units (LUFS, dBTP) and the ITU-R BS.1770 standard, making the tool's purpose unambiguous and distinguishable from generic render or analysis siblings.
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?
Usage is implied by the measurement purpose, but the description does not explicitly say when to use this tool versus siblings like analyze_dynamics, detect_clipping, normalize_project, or render_project. There are no exclusions or alternative-selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.