mcp_opendaw_export_stems

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

With no annotations, the description covers internal mechanism (OfflineEngineRenderer, per-AU ExportConfiguration) and output (list of stem files). It does not detail side effects like file overwriting, but for a read-like export tool this is adequate.

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?

Four focused sentences plus a workflow line, no filler. Front-loaded with the core action.

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?

Describes workflow and return type, but missing parameter semantics limits completeness. Output schema exists but doesn't offset parameter gap.

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% and the description adds no detail on filename_prefix format or sample_rate expected range/units. Both required parameters lack semantic clarification.

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 verb ('Export'), resource ('each audio unit as a separate stem WAV file'), and differentiates from sibling tools like export_dawproject or export_midi.

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?

Description provides a concrete workflow chain (create_instrument_track → load_audio → place_audio_region → add_effect → export_stems), guiding when to use this tool. However, it does not explicitly mention when not to use or alternatives like export_single_stem.

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