mcp_opendaw_render_full_format

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It notes that MP3/FLAC conversion uses system ffmpeg and that the tool returns both WAV and converted file paths. However, it does not mention potential side effects, prerequisites (e.g., engine running), or constraints (e.g., project must be fully loaded). Given these gaps, the transparency is moderate.

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 extremely concise: a single-sentence header, a bullet-like param listing, and a summary line. Every sentence provides necessary information without redundancy. It is front-loaded with the core purpose and structured for easy parsing.

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 has 4 parameters and an output schema, the description covers the key aspects: purpose, parameter semantics, the combined operation, and ffmpeg dependency. It lacks mention of prerequisites (e.g., project state) and error handling, but these might be covered by the output schema. Overall, it is fairly complete for a tool of moderate complexity.

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 must fully explain parameters. It does so effectively: clarifies that filename expects no extension, defines default sample_rate (48000), lists format options (wav/mp3/flac) with a note about ffmpeg dependency, and explains that bitrate is ignored for WAV/FLAC. This adds substantial value beyond the schema's default values alone.

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's purpose: 'Render the entire project and convert to MP3 or FLAC in one step.' It specifies a concrete action (render+convert) and the resource (entire project). This distinguishes it from sibling tools like mcp_opendaw_render_full and mcp_opendaw_convert_audio, which handle only part of this workflow.

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 mentions that it combines 'render_full + convert_audio' and lists parameter details, which implicitly guides when to use it (for one-step render and format conversion). However, it does not explicitly state when not to use it (e.g., if only WAV is needed, render_full may be sufficient) or provide alternatives. Guidance is adequate but not comprehensive.

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