mcp_opendaw_render_full

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

With no annotations, the description carries the full transparency burden. It discloses the internal rendering mechanism (OfflineEngineRenderer with Option.None), the exact time range rendered, and the return payload (path and audio metadata). It does not mention potential side effects like file overwriting, but for a render operation this is solid behavioral disclosure.

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 tightly structured: a one-sentence purpose, a brief parameter list, and two implementation/behavior details. Every sentence adds value, and the most important information is front-loaded.

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?

The description covers the purpose, both parameters with usage semantics, the exact render range, the rendering engine used, and the return format. With an output schema available for the return value, this is a complete and self-contained description for a two-parameter 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 schema provides defaults for both parameters, but the description adds value by clarifying that filename should be given without the .wav extension and restating the default sample rate. This helps the agent avoid common errors, going beyond the raw schema.

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+resource+scope: 'Render the entire project as a single stereo WAV file (full mixdown).' This clearly distinguishes it from range renders, stem exports, and other audio export tools by emphasizing the full mixdown scope and single-file output.

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 gives clear context: it renders the full project from beat 0 to the last region, and is intended for a full mixdown. However, it does not explicitly name alternative tools (e.g., export_mix, render_range) or state when not to use it, so it stops short of a full usage guide.

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