mcp_opendaw_subdivide_notes

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

With no annotations, the description carries the full burden and delivers extensively. It discloses that 'Original notes are replaced in place when same track,' explains the override behavior (accent_first overridden by velocity_pattern), and details the effects of pitch and velocity patterns. This goes far beyond a basic statement and gives the agent concrete expectations.

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: an opening summary, a use-case paragraph, and a clear Args block. Every sentence serves a purpose, providing necessary detail without fluff. It is longer than some, but the tool's complexity (8 parameters, multiple pattern options) justifies the length. The most important information is front-loaded.

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, no annotations, and the presence of an output schema, the description covers all necessary ground: purpose, usage context, parameter semantics, and behavioral effects (replacement, overrides). Return values are presumably handled by the output schema, so the absence of that info is not a gap. This is a fully realized description.

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 no property descriptions (0% coverage), so the Args section in the description is essential. It explains every parameter with meaningful detail: examples for subdivisions (2=diminution, 4=sixteenth fragmentation), enumerates all pitch and velocity pattern options, and clarifies default behaviors like region_index=-1 meaning first region. This adds substantial value beyond the bare 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 a specific action: 'Subdivide each note in a region into N smaller notes,' clearly identifying the verb, resource, and scope. It also distinguishes this tool from siblings by emphasizing its use for diminution and rhythmic fragmentation, which differentiates it from tools like create_chop or double_melody.

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 on when to use the tool: 'Useful for diminution (quarter → 2 eighths), rhythmic fragmentation, and creating faster passagework from longer notes.' However, it does not explicitly state when not to use it or reference alternative sibling tools, so it stops short of full explicit guidance.

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