mcp_opendaw_analyze_dynamics

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

The readOnlyHint annotation already declares the tool safe, and the description adds substantial context about the metrics, the 10-segment RMS contour, and compression suggestions. It also clarifies the input format (WAV file in exports directory or absolute path). No contradictions with annotations. A 5 would require even richer operational detail, but this is solid.

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 structured logically: a one-line summary, a bulleted metric breakdown, compression guidance, argument explanation, and return summary. Every sentence carries useful information—no fluff. Despite length, it is efficiently organized and scannable for an agent.

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 multi-metric analysis tool, the description covers everything: what the tool does, the meaning of each metric, interpretation thresholds, input specification, and return content. The output schema further enriches context, so the description need not restate structured return types. This is complete for informed selection and invocation.

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 input schema has no description for 'filename', but the description fully compensates: 'Name of the WAV file in the exports directory (without path), or absolute path to any WAV file.' It resolves ambiguity about path resolution and file type, adding meaning beyond the schema's bare 'Filename' title.

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 performs 'Dynamics analysis' with specific metrics (crest factor, loudness range, transient density, segment RMS) and 'Measures the dynamic character of a track.' This specific verb+resource combination distinguishes it from siblings like analyze_spectrum, analyze_stereo, and measure_lufs.

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 detailed compression decision guidance with quantitative thresholds (e.g., 'crest_factor < 6 dB → heavily compressed'), which implies when to use the tool for dynamic evaluation. However, it does not explicitly name alternative tools for other analysis types, so it stops short of the 'explicit alternatives' bar for a 5.

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