generate_drum_pattern

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

No annotations exist, so the description carries full burden. It describes the action but doesn't disclose whether existing notes in the clip are overwritten or appended, what happens if the track isn't a drum track, or any side effects. This ambiguity is significant for a generative mutation tool.

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?

Four-line description followed by a compact parameter list. Every sentence adds value, front-loaded with the purpose, no 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?

Covers core purpose and parameters, but lacks crucial details for reliable use: overwrite vs append behavior, error handling, and effect on existing clip contents. Without annotations or output schema, these gaps make the tool incomplete for an agent to confidently predict outcomes.

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 parameter descriptions in the tool description are the only semantic source. It explains each parameter meaningfully: style examples, length in beats, and the drum track constraint. It doesn't provide enum ranges or constraints, but adds substantial value beyond raw 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?

Clearly states it generates a drum pattern and adds it to a clip, with specific target tracking via track_index and clip_index. It doesn't explicitly distinguish itself from the similar generate_bassline tool, but the resource and action are specific enough.

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?

Provides context that track_index should be a drum track, which implies when this tool is appropriate. However, it doesn't explicitly state when NOT to use it or name alternatives like generate_bassline, so it misses the exclusion part.

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