generate_and_place_drums

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

Discloses GM drum mapping and pattern/variation behavior. No annotations exist, so description carries full burden. Does not mention that replace_existing parameter will overwrite notes or any side effects. No annotation contradiction.

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?

Short, focused description with front-loaded purpose. Every sentence adds value: verb+resource, GM mapping, pattern options, variation explanation. 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?

With 8 parameters, 0% schema coverage, and no annotations, the description only covers pattern and variation. Missing explanations for track_index, slot_index, style, length_bars, replace_existing, seed. Output schema exists but does not reduce need for parameter clarity.

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?

Description adds meaning for 'pattern' (lists options) and 'variation' (range 0-1) which the schema lacks. However, 0% schema coverage means other parameters (track_index, slot_index, style, length_bars, replace_existing, seed) are not explained in description or schema. Partial compensation.

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 'Generate a drum pattern and place it into a MIDI clip' with specific verb (generate and place), resource (drums), and context (MIDI clip). Distinguishes from sibling generation tools by focusing on drums and mentioning GM drum mapping.

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?

Implies usage for drum pattern generation but does not explicitly state when to use this tool vs alternatives like generate_and_place_arpeggio or other pattern generators. Mentions a prerequisite (set up Drum Rack) but lacks comparison or exclusionary guidance.

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