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

With no annotations, the description carries the full burden. It discloses that notes are created for riser and snare roll, explains the velocity ramp and density increase, and details unit_index default behavior. It does not mention failure modes or whether existing notes are overwritten, but it is quite transparent for a creative generator.

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 with a summary, component breakdown, style presets, parameter explanations, return value, and a practical example. Every sentence adds value; the style list is necessary detail rather than 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?

The description covers purpose, usage, parameters, return value, and provides an example. It lacks explicit details on where the snare roll is placed relative to the riser track, and error conditions for missing note tracks, but overall it gives enough guidance for an AI agent to invoke the tool correctly.

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 – and it does thoroughly. Every parameter is explained with additional context: style presets include exact note patterns, velocity has a 0-1 range and ramp behavior, unit_index explains the -1 behavior, and length_beats defaults to 8 = 2 bars.

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 a complete build-up — riser + snare roll in one call,' which clearly states the verb, resource, and scope. It explicitly distinguishes from the sibling create_riser by emphasizing the combination of two elements.

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?

It says the tool is for 'a full build-up before a drop/chorus' and the example shows it used before create_impact, giving clear context. It does not explicitly state alternatives or when not to use it, but the genre-specific style options imply usage across different musical contexts.

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