mcp_opendaw_create_trap_arrangement

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

The description discloses the musical output (notes, tracks, patterns) and return value ('Returns notes created per track and total'), but it does not clarify operational behavior such as whether existing notes on the target tracks are overwritten, whether tracks are expected to exist beforehand, or if the tool creates new tracks. With no annotations to rely on, these are meaningful gaps for a mutation tool that writes 3 tracks of notes.

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 with an initial summary, bullet points for track content, a parameter list, output note, and examples. It is slightly verbose due to repeated emphasis on the 808 bass's musical character, but for a tool with 10 parameters the length is justified and information is front-loaded.

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's complexity (10 params, no annotations, output schema present but not detailed), the description covers the main functionality, parameter meanings, and examples, but leaves two parameters unexplained and does not state prerequisites (e.g., whether note tracks must exist or be empty). These are clear gaps for a creative generation tool that writes to specific tracks.

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 description compensates for the 0% schema description coverage by explaining 8 of the 10 parameters with concrete ranges, defaults, and musical context (e.g., 'octave: MIDI octave for 808 bass (1 = C1=24)', 'root: Root note (F# minor is the most common trap key)'). However, it omits 'velocity' and 'start_beat', which remain undocumented in both the schema and description.

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 a specific action ('Create a full trap arrangement') with a defined scope ('drums + 808 bass + bell melody across 3 tracks in one call'). It distinguishes itself from sibling arrangement tools by naming the exact genre and characteristic elements like 'trap hi-hat rolls' and '808 sub-bass slides'.

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 contextual guidance for when to use this tool: to generate a modern trap arrangement. It gives concrete parameter guidance with ranges and defaults ('bpm: Tempo (130-160, default 140)', 'bars: Arrangement length (4-32)'), plus usage examples. It does not explicitly mention alternatives for other genres, but the naming and context make the intended use obvious.

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