mcp_opendaw_render_full_format

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 the return values ('Returns both WAV and converted file paths'), the dependency on system ffmpeg, default sample rate, and that bitrate is ignored for WAV/FLAC. It could go further (e.g., potential runtime, side effects), but the provided transparency is solid.

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 compact and efficient: a purpose sentence, parameter explanations, and a final sentence covering combination and return. No fluff or repetition; every line earns its place.

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's moderate complexity (4 optional params, no required fields), an output schema, and no annotations, the description is comprehensive. It covers purpose, parameters, dependencies, and return values. Missing usage exclusion is the only small gap, already captured in usage_guidelines.

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 fully compensates. It explains each parameter meaning beyond defaults: filename ('without extension'), sample_rate, format values and defaults, bitrate behavior including 'Ignored for WAV/FLAC'. This adds significant value over 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 and resource: 'Render the entire project and convert to MP3 or FLAC in one step.' It also explicitly notes it 'Combines render_full + convert_audio,' which clearly distinguishes it from sibling rendering and conversion tools.

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 for when to use this tool (when a one-step full-project render and format conversion is needed) and references the two underlying operations, 'render_full + convert_audio.' However, it does not explicitly state when NOT to use it or list alternative tools for WAV-only or conversion-only tasks.

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