gen_emit_drum_pattern_notes

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

No annotations provided. Description mentions it emits notes to piano roll but does not disclose if it clears existing notes (though parameter clear_first exists but is not described). Does not explain side effects or permissions. Adequate but not comprehensive.

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?

Extremely concise: one short paragraph with purpose, usage, and parameter notes. No redundant information. Front-loaded with key action and prerequisite.

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?

Missing descriptions for step_bars, repeats, and clear_first parameters. No output schema information. Does not compare to sibling tool gen_emit_drum_pattern_step_seq. Incomplete for a tool with 5 parameters and no annotations.

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 coverage is 0%. Description explains only 2 of 5 parameters (midi_map with defaults, style reference). Parameters step_bars, repeats, and clear_first are not described, leaving significant gaps for agent usage.

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?

States 'emit a drum groove to the currently-open piano roll as individual notes' with clear verb and resource. Distinguishes from sibling gen_emit_drum_pattern_step_seq by specifying 'when you don't have a MIDI bridge (no step sequencer access)'.

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 states when to use: 'Use this when you don't have a MIDI bridge (no step sequencer access).' Provides prerequisite: 'Open the drum channel's piano roll first.' No explicit when-not to use, but context is clear.

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