mcp_opendaw_transfer_audiounit

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

With no annotations, the description carries the full burden. It discloses the deep-copy mechanism, dependencies, delete_source for move semantics, and the output unit limitation. It could elaborate on side effects like routing or use cases, but this is solid coverage.

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 well-structured and front-loaded with purpose, followed by implementation details, parameter explanations, and return info. Some jargon like 'box-graph serialization' is not essential, but the description remains efficient.

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?

The description covers purpose, behavior, parameters, and return values. It lacks explicit prerequisites (e.g., project loaded) and broader comparison to all sibling tools, but for a complex transfer operation, this is sufficiently 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 description coverage is 0%, so the description must explain everything. It does so effectively: unit_index, delete_source (move semantics), insert_index (position, -1 auto-place). This fully compensates for the missing schema descriptions.

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 transfers/copies an audio unit with all dependencies, using a specific verb and resource. It explicitly distinguishes from duplicate_audiounit, making the purpose unambiguous.

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 provides clear context (deep-copy with dependencies) and explicitly names duplicate_audiounit as an alternative, noting it is less complete. However, it does not discuss exclusions or when to use other sibling tools like transfer_region or move_audio_unit.

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