gen_emit_drum_pattern_step_seq

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

With no annotations, the description carries the full burden. It mentions the MIDI bridge requirement but fails to disclose important behaviors like whether the tool overwrites existing patterns, potential side effects, or error handling. The mutation action is implied but not elaborated.

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 short (two sentences) and front-loaded with the main action. Every sentence adds value, though the structure could be improved by separating parameter documentation more clearly.

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 the complexity (4 params, nested object, no output schema, no annotations), the description is incomplete. It lacks behavioral details, parameter semantics for most params, and any return value information.

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?

The description explains the 'channel_map' parameter (mapping drum names to channel indices), which adds meaning beyond the schema. However, the other three parameters (style, repeats, pattern) have no description coverage and are not explained, leaving a significant gap.

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 verb 'Write' and resource 'drum groove into the step sequencer', and distinguishes from sibling tool 'gen_emit_drum_pattern_notes' by specifying the target (step sequencer vs. notes).

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 provides a prerequisite ('requires MIDI bridge') and hints at when to use ('when you DO have a MIDI bridge'), but does not explicitly state when not to use or mention alternatives (e.g., using gen_emit_drum_pattern_notes without a bridge).

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