mcp_opendaw_create_metal_arrangement

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

With no annotations, the description carries full behavioral disclosure. It details per-track behavior, scale choices, and explicitly states the return value ('Returns notes created per track and total'). However, it does not disclose whether the tool appends to existing notes or overwrites tracks, nor does it fully clarify prerequisites beyond 'unit_index: AU index with note tracks.'

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 organized clearly: purpose, track breakdown, BPM context, riff theory, parameter list. It front-loads the main point and uses bullet points for readability. Some stylistic flourishes (e.g., 'relentless heartbeat of metal') add flavor but not operational value, making it slightly less concise than ideal.

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 complex tool that creates four tracks of arrangement, the description covers the compositional approach, musical style, key parameters, and expected return. Given that an output schema exists, it does not need to document return syntax in detail. Gaps include velocity, start_beat, and interaction with existing notes, but overall the description provides sufficient context for an AI 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?

Schema description coverage is 0%, so the description is the only source of parameter meaning. It explains bpm, bars, root, octave, unit_index, and all four track indices with ranges and defaults, which is substantial. However, it omits velocity and start_beat entirely, leaving those 2 of 11 parameters unexplained.

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+resource: 'Create a full metal arrangement — double kick drums + palm-muted riffs + power chords + shred lead.' It clearly enumerates the four tracks, making the tool's function unmistakable and distinguishing it from the many other genre arrangement tools in the sibling list.

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 strong usage context: BPM ranges map to subgenres (120=traditional metal, 160=thrash, 200+=extreme), and it emphasizes riff-based rather than chord-progression-based composition. It does not explicitly mention alternatives, but the tool's purpose is so clearly scoped that 'use for metal arrangements' is unambiguous.

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