mcp_opendaw_export_mix

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

Without annotations, the description carries the burden. It discloses that it uses offline rendering (faster, no engine), explains the method parameter's actual behavior, and mentions output includes path and metadata. However, it does not address potential side effects like file overwriting or project state requirements.

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 the main action and key details front-loaded. It could be more structured with per-parameter bullet points, but overall it is efficient without wasted words.

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?

With an output schema available, the description need not detail return values. It covers the main purpose, method behavior, and parameters. However, it lacks information on prerequisites (e.g., project must be loaded), error conditions, or asynchronous behavior. For a tool with many siblings, more context on when to use it would be beneficial.

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 coverage is 0%, so the description compensates well by explaining each parameter: filename (without .wav extension), sample_rate (default 48000), and method (always uses offline regardless of value). This adds meaning beyond the schema's types and defaults.

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 full project mix to a WAV file, with specifics about using OfflineEngineRenderer and the method parameter's backward compatibility. However, it does not explicitly distinguish itself from render_full or other export tools like export_stems, which could cause ambiguity.

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?

No explicit guidance on when to use this tool over alternatives like render_full or export_stems. No prerequisites or scenarios mentioned. The description only states what it does, not when to choose it.

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