generate_groove

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

The description adds context beyond the destructiveHint annotation by explaining that existing notes are replaced and detailing the effects of parameters like pocket, swing, ghost, and humanize. It would benefit from mentioning undo behavior or side effects.

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 concise at 4 sentences, front-loaded with purpose and destructiveness, followed by parameter explanations. Every sentence adds value without redundancy.

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 9 parameters and 0% schema description coverage, the description covers the core generative parameters but misses scaffolding parameters (bars, seed, track_index, clip_index). The existence of an output schema reduces the burden for return values, but parameter coverage could be more complete.

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?

With schema description coverage at 0%, the description explains 5 of 9 parameters (style, pocket, swing, ghost, humanize) with ranges or examples. However, it omits bars, seed, track_index, and clip_index, leaving gaps for a tool with many 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 it writes a pocketed drum groove into a Session clip and replaces existing notes. It mentions specific parameters and the standard Live drum map, which distinguishes it from siblings like generate_drum_pattern or generate_bassline.

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 warns that the tool REPLACES existing notes, implying destructive use, but does not explicitly state when to use this tool versus alternatives like write_drum_grid or generate_drum_pattern. Usage context is implied rather than direct.

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