mcp_opendaw_create_motif_development

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

With no annotations, the description carries full behavioral disclosure burden. It reveals key traits: writes a single continuous line (not separate regions), flows through stages without stopping, and returns 'total notes, stage count, pitches used.' It doesn't mention whether existing notes are overwritten or merged, but given the depth of process description, it is largely transparent.

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 substantial but every sentence adds value: overview, motivational context, sibling differentiators, and parameter explanations are well-structured and front-loaded. The 'Beethoven 5th' analogy is concise and memorable. No filler or redundant repetition of schema defaults.

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, 0% schema coverage), the description is highly complete. It explains the composition stages, provides examples, lists return values, and states the track/AU requirements ('unit_index: AU index with a note track'). It is more than sufficient for an AI agent to correctly select and invoke this tool.

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 fully compensates for every parameter. It explains motif format with examples ('1,1,1,2' vs '60,60,60,62'), defines each development step (sequence_up, fragment, invert, etc.), and clarifies scale, root, octave, step_duration, velocity, unit_index, track_index, and start_beat. This is far beyond what the schema alone provides.

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: 'Develop a motif into a through-composed melodic line that evolves.' It clearly explains the tool transforms a short motif (2-8 notes) into a continuous melodic line through named compositional stages. It also explicitly distinguishes itself from create_variations and create_sequence, which are sibling tools.

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 includes explicit usage guidance: 'Unlike create_variations... create_motif_development writes ONE continuous line' and 'Unlike create_sequence (pure transposition), this tool mixes multiple development techniques.' This tells the agent exactly when to choose this tool over alternatives. It also gives the 'Beethoven 5th approach' analogy as real-world context.

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