generate_euclidean_drums

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

The description explicitly states REPLACES existing notes (destructive), explains the Euclidean distribution, rotation, humanization, and instrument mapping. This adds significant context beyond the destructiveHint annotation.

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 with two sentences front-loading the main action. However, the second sentence is a run-on list of parameter explanations, slightly lacking structure.

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 (10 params, no schema descriptions) and the presence of an output schema and annotations, the description provides enough context for most users. Missing seed and velocity details slightly reduce completeness.

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 most parameters (steps, pulses, rotate, bars, humanize, instrument) but misses seed and velocity. Since schema coverage is 0%, the description should cover all parameters; missing two is a notable 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 tool writes a Euclidean (Bjorklund) rhythm into a Session clip, specifying the algorithm and how parameters affect the pattern. It distinguishes itself from siblings like generate_drum_pattern by the Euclidean algorithm focus.

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 implies usage for Euclidean rhythms but does not explicitly guide when to use this tool versus alternatives like generate_drum_pattern or write_drum_grid. No when-not-to-use or alternative names are provided.

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