mcp_opendaw_create_riff

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not specify side effects like whether existing notes are overwritten or appended, nor does it clarify the role of parameters like track_index and unit_index in placement. The musical behavior is well-described, but operational transparency is lacking.

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: a one-line summary, definition, genre details, parameter list, and examples. It front-loads the purpose. However, the genre sections are somewhat verbose (e.g., artist lists), and some sentences could be condensed. Overall, it efficiently imparts necessary information.

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?

With an output schema present, the description need not explain return values. It thoroughly covers musical intent and genre-specific behaviors, but it omits operational details like where the riff is placed (track, unit, beat) and fails to describe all parameters. For a 10-parameter tool, this leaves noticeable gaps.

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 has 0% parameter descriptions, so the description must compensate. It explains 7 of 10 parameters (riff_type, key_root, scale_type, bars, octave, velocity, seed) with meaningful context (e.g., octave range for guitar). However, start_beat, unit_index, and track_index are not mentioned, leaving critical placement parameters undocumented.

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 'Create a genre-specific riff — catchy repeated melodic fragment.' It then defines a riff in contrast to melody and ostinato, distinguishing it from sibling tools like create_melody or create_ostinato. This precise differentiation and strong verb-resource pairing earn a top score.

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 genre-specific guidance and examples (e.g., rock, funk, metal) and contrasts riff with melody/ostinato, which helps the agent decide when this tool is appropriate. However, it lacks explicit 'when to use' or 'when not to use' directives, such as prerequisites or alternatives, so it does not fully reach a 5.

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