mcp_opendaw_render_range

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

No annotations are provided, so the description carries the full burden. It discloses the underlying implementation ('Uses OfflineEngineRenderer with custom range'), the output ('Returns the path to the exported WAV and audio metadata'), and the speed benefit. It does not explicitly state that rendering is non-destructive, but as an export operation this is largely implied and no contradictory behavior is hinted.

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 well-structured and efficient: a one-sentence purpose, a concise parameter list, an implementation note, and the return value. Every sentence provides value with no filler. The purpose is front-loaded, making it easy for an agent to scan.

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?

Given the tool's moderate complexity (4 parameters, all documented), the presence of an output schema that covers return values, and the clear usage context, the description is complete. It even includes an internal implementation detail and a performance comparison, which helps the agent reason about when to choose this tool over full renders.

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%, but the description compensates fully by explaining every parameter: start_beat (with '0 = project start'), end_beat, filename (without .wav extension), and sample_rate (with default). This adds concrete meaning beyond the bare schema field names and types.

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 opens with a specific verb and resource ('Render only a portion of the project') and gives a concrete example ('chorus only'). It clearly distinguishes itself from full-export tools by explicitly limiting scope to a range, which is reinforced by the tool name and sibling names.

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 clear usage context: 'for quick A/B comparison' and 'Faster than full export for checking specific sections during mixing.' It implies when to use it (section-level mixing checks) but does not explicitly name alternative tools or describe when not to use it, though the comparison to full export gives sufficient guidance.

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