mcp_opendaw_create_riff

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

With no annotations provided, the description must disclose behavioral traits. It describes musical style and parameter ranges, but never states whether the operation writes to a track, overwrites existing notes, requires permissions, or is reversible. The lack of side-effect disclosure is a significant gap for a creation tool.

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 a clear opening, genre bullet points, parameter list, and examples. Each section serves a purpose, though it is longer than minimal; the genre details and examples add value but could be trimmed without losing the core message.

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 the musical concept and primary parameters, but it completely omits the placement parameters (start_beat, unit_index, track_index), leaving agents uncertain how the riff integrates with a track or region. It also does not clarify whether the riff is appended, replaces existing notes, or creates a new region, making the invocation context incomplete.

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 schema provides zero property descriptions, so the description compensates by explaining riff_type, key_root, scale_type, bars, octave, velocity, and seed, including allowed values and defaults. However, it omits start_beat, unit_index, and track_index, leaving those parameters underexplained despite being in the schema.

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 'Create a genre-specific riff — catchy repeated melodic fragment,' a specific verb+resource statement. It further distinguishes a riff from a melody and an ostinato, clearly separating this tool from siblings like create_melody and create_ostinato.

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 for when to use this tool by contrasting riff against melody and ostinato, and it gives genre-specific guidance with examples. However, it does not explicitly name alternative tools or state when not to use this tool, so it lacks explicit exclusions.

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