gen_emit_dnb_groove

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

No annotations are provided, so the description must fully disclose behavior. It explains the MIDI mapping and loop structure, but omits side effects (e.g., whether it clears existing notes, appends, or overwrites) and does not mention what happens if no piano roll is open.

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 two sentences long, front-loading the primary purpose. It is concise with no unnecessary words, though a bit more structure (e.g., listing parameters) would improve clarity.

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 three parameters, no output schema, and no annotations, the description is incomplete. It fails to explain two of the three parameters and does not clarify the tool's interaction with the open piano roll or potential destructive actions, making it hard to use 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. It only explains the 'repeats' parameter (2-bar loop, default 2). The 'style' enum and 'clear_first' boolean are not described, leaving their meaning ambiguous.

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 clearly states the tool emits a Drum & Bass drum groove to the open piano roll using specific MIDI note numbers (36 kick, etc.). It distinguishes from sibling tools like gen_emit_bassline or gen_emit_melody by specifying the genre and resource.

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 explains that a 'repeat' is a 2-bar loop and default is 4 bars, but does not specify when to use this tool versus alternatives (e.g., gen_emit_drum_pattern_notes) or any prerequisites like an open piano roll being required.

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