mcp_opendaw_export_effect_chain

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

No annotations present, so the description carries full burden. It discloses that it uses PresetEncoder.encodeEffects and returns base64 bytes or error, but does not explicitly state that the operation is non-destructive or read-only. The behavioral transparency is adequate but not thorough.

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: three sentences plus parameter explanations, front-loading the purpose. No redundant information; every sentence adds value.

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 2 parameters, no annotations, and an output schema, the description covers the return value (base64 preset bytes), the internal encoder, and forward reference to import_effect_chain. It omits context about the AU (likely an audio unit/device), but is otherwise complete.

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 by explaining unit_index (AU index to export from) and effect_type (audio or MIDI, with default 'audio'). It adds meaning beyond the schema but lacks indexing convention (e.g., 0-based or 1-based).

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 exports an effect chain as a base64 preset. It distinguishes from siblings like export_preset (exports a single preset) and import_effect_chain (imports), specifying audio or MIDI chains.

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 mentions the preset can be imported via import_effect_chain, hinting at a use case. However, it does not explicitly say when to use this over alternatives like clone_effect_chain or export_preset, nor does it provide when-not-to-use guidance.

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