mcp_opendaw_create_trap_rolls

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

The description discloses return values and velocity offsets, but does not state whether notes are appended or replace existing notes, nor does it explain track_index, start_beat, or unit_index behavior. With no annotations, these operational details are missing, making the tool's DAW side effects unclear.

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 thorough and logically structured (purpose, roll types, parameters, return, example), but is longer than necessary with cultural references and song examples. It is front-loaded with the core action, so it remains readable.

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 9-parameter tool with no schema descriptions and no annotations, the description covers the musical style thoroughly but leaves out operational essentials (track targeting, start position, unit context). The presence of an output schema is mentioned but its structure isn't described, so the agent still lacks full invocation clarity.

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 adds deep meaning for roll_type (five styles with rhythmic breakdowns), plus pitch and velocity semantics. However, three parameters (start_beat, unit_index, track_index) are entirely unexplained in the description, leaving critical placement information to the schema, which also lacks descriptions.

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 trap hi-hat roll patterns' and provides detailed variants (modern, migos, bubble, skrrt, evolving), clearly distinguishing this from generic drum tools. It specifies the resource (trap hi-hat rolls) and the verb (create), making the tool's purpose unambiguous.

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 implies usage for trap production with specific style examples, but does not explicitly contrast with sibling tools like create_drum_pattern or create_trap_arrangement. It gives within-tool guidance for choosing roll_type, but no when-to-use vs alternatives.

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