mcp_opendaw_export_mix

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

With no annotations provided, the description carries the full burden. It discloses that all method values effectively use offline rendering, that filename should omit the .wav extension, and that it returns the path and audio metadata. This adds meaningful behavioral context beyond the schema, though it omits potential side effects (likely non-destructive for an export).

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 organized with a one-sentence summary, engine note, then a parameter list. It is slightly verbose but every sentence adds value. The 'same as render_full' phrase is useful context rather than redundancy.

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 tool has an output schema, but the description still mentions the return type, which is helpful. It explains the method parameter's real behavior and defaults, and covers the key aspects for a straightforward export operation. Missing only explicit error conditions or prerequisites, but the description is sufficient for a simple 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?

Schema description coverage is 0%, so the description's parameter explanations are essential. It clearly defines filename (without extension), sample_rate default, and the method parameter's accepted values and actual behavior (all use offline). This fully compensates for the missing schema documentation.

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 'Render the full project mix to a WAV file' – a specific verb and resource. It also references render_full for engine context, distinguishing it from other render/export tools. Name and description align well.

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 implies usage for full-mix WAV export but does not explicitly state when to prefer this over render_full, export_stems, or other render tools. It mentions backward compatibility but provides no exclusions or alternatives, leaving the agent to guess based on partial context.

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