mcp_opendaw_subdivide_notes

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

With no annotations, the description carries full burden. It discloses that original notes are replaced in place when dest_track_index=-1, and that accent_first is overridden by velocity_pattern. However, it does not state whether the operation is destructive or reversible, nor any performance or constraint implications (e.g., note overlap, time boundaries).

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 concise intro, a use-case sentence, then a clear Args list. It is slightly verbose in the Args (e.g., repeating 'original'), but all sentences add value. Could be tightened without loss.

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 complexity (8 params, 2 required, output schema exists) and many siblings, the description covers inputs, behavior, and use cases well. It does not describe the output (though output schema exists), but that is acceptable. It lacks mention of time signature or tempo constraints which might affect subdivision.

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%, but the description's Args section provides detailed explanations for all 8 parameters, including example values and effects (e.g., subdivisions: '2=diminution, 4=sixteenth fragmentation, 3=triplet subdivision'). This adds significant meaning beyond the schema titles.

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 action: 'Subdivide each note in a region into N smaller notes.' The verb 'subdivide' and resource 'note region' are specific. It distinguishes itself from sibling tools like 'augment_notes' or 'apply_velocity_pattern' by focusing on rhythmic fragmentation.

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?

Explicitly says 'Useful for diminution, rhythmic fragmentation, and creating faster passagework from longer notes,' giving clear context. However, it does not provide when-not-to-use guidance or compare with alternatives like 'consolidate_note' or 'repeat_notes', which could help the agent choose correctly.

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