generate_drum_pattern

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

No annotations provided, so description must disclose behavior. It mentions generating and adding a pattern but omits details like whether existing notes are overwritten, default style effects, or what happens if track is not a drum track.

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?

Highly concise with one-line summary followed by bullet list of parameters. No redundant information, well-structured for quick parsing.

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 basic purpose and parameters but lacks behavioral context (e.g., what happens to existing clip notes) and return value. Without output schema, more detail on the generated pattern could help.

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?

Adds meaning beyond schema by describing each parameter (e.g., track should be drum, length in beats, style options). However, it lacks details like valid ranges for length or units, and doesn't explain interaction between parameters.

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 generates a drum pattern and adds it to a clip. It distinguishes from sibling 'generate_bassline' by specifying drum, but does not explicitly differentiate from other clip manipulation tools.

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?

No guidance on when to use this tool versus alternatives like 'add_notes_to_clip' or 'generate_bassline'. Prerequisites (e.g., existing drum track) are only implied in parameter hints, not explicitly stated.

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