mcp_opendaw_render_full

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

No annotations are provided, so the description carries full burden. It discloses the engine used, the absence of stems configuration, the full project range, and the return value (path and audio metadata). This is reasonably transparent for a render operation, though it does not mention potential side effects or errors.

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 concise with two short paragraphs. The first sentence clearly states the purpose, followed by parameter explanations and technical details. Every sentence adds value without unnecessary fluff.

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 presence of an output schema (has_output_schema: true) and two simple parameters, the description is largely complete. It explains the rendering scope, engine, and return value. Minor details like error handling are absent but not critical for a straightforward render tool.

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 0% description coverage, but the description compensates by explaining both parameters: filename (without .wav extension) and sample_rate (with default 48000). This adds meaning beyond the schema's titles and defaults, making the tool easier to use correctly.

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 renders the entire project as a single stereo WAV file (full mixdown). The verb 'render' and resource 'entire project' are specific, and it distinguishes from siblings like render_and_analyze or render_range by emphasizing full mix without stems.

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 explains the technical approach (OfflineEngineRenderer with Option.None) and the rendering range (beat 0 to end of last region), but does not explicitly state when to use this tool versus alternatives like render_full_song or render_full_format. Usage context is implied rather than explicit.

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