mcp_opendaw_create_dembow

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

With no annotations provided, the description carries the burden of explaining behavior. It discloses the pattern structure for each dembow variant, the velocity adjustments, and that the tool returns notes created, dembow type, and stroke breakdown. However, it does not mention potential side effects like whether existing notes on the target track are overwritten or how it interacts with the current project state.

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 relatively long but well-organized with a clear opening, a musical background, enumerated variants, and parameter details. Each section earns its place, and the examples add practical value without excessive fluff.

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 (8 parameters, no annotations), the description is quite complete: it defines dembow, lists variants with exact beat positions, explains pitch and velocity defaults, and provides examples. Missing details on start_beat and unit_index prevent a perfect score, but the overall context is sufficient for most use cases.

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 must compensate. It thoroughly explains dembow_type, velocity, bars, kick_pitch, and snare_pitch, and shows track_index in examples. However, start_beat and unit_index are left entirely undocumented, leaving a significant gap for two of the eight parameters.

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 the tool's purpose: 'Create a dembow rhythm — the foundational beat of reggaeton and Latin dancehall.' It uses a specific verb and resource, and the detailed explanation of what a dembow is and its variants (classic, dancehall, trap_latino, etc.) distinguishes it from the many other rhythm-creation tools in the sibling list.

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 the tool should be used when a dembow rhythm is needed, providing context on the pattern's musical role and examples of usage. However, it does not explicitly state when not to use it or contrast it with alternative tools like create_clave or create_boom_bap, so it stops short of a full usage guide.

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