mcp_opendaw_convert_audio

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

With no annotations, the description carries the full burden. It discloses that system ffmpeg is required (not browser WASM), that it falls back gracefully if missing, and that it returns the path and size info. It does not detail overwrite behavior or failure modes, but the key operational traits are covered.

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 well-structured: a one-sentence summary, a tight parameter list, then dependency and return information. Every line adds value and there is no filler or repetition.

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?

For a moderate conversion tool, it covers the source location, target formats, parameter defaults, system requirement, fallback behavior, and return value. The fallback statement is a bit vague ('falls back gracefully' without specifying the actual behavior), and it doesn't mention output destination or filename conventions, but the presence of an output schema and the existing detail make it functionally complete for an agent.

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 has zero descriptions for its 4 parameters, but the description documents each one thoroughly: filename (source, without .wav, in export dir), format (mp3/flac, default mp3), bitrate (MP3 CBR, default 320k, ignored for FLAC), and quality (VBR 0-9, -1 for CBR, default). This adds complete meaning beyond the bare 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: 'Convert an exported WAV file to MP3 or FLAC using system ffmpeg.' This clearly distinguishes the tool from siblings like export_mix or download_audio by stating its exact purpose and target formats.

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?

It provides clear context: source is an exported WAV file in the export dir, and it notes the requirement for system ffmpeg with graceful fallback. It does not explicitly name alternatives or exclusion cases, but the scope (WAV to MP3/FLAC) and prerequisites are clear enough for an agent to decide when to use it.

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