add_notes_pattern

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

With no annotations, the description carries the full burden and does well: it discloses that notes are added in a single Live undo step, that existing notes remain, that per-note validation matches add_notes_to_clip, and that pitch/velocity are clamped. It does not describe error responses or the return payload, but the mutation and undo semantics are clearly covered.

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?

Well front-loaded: purpose, then side effects, then a concrete example, then edge cases. Every section adds signal. The example line is slightly dense but earns its place by demonstrating several parameters at once.

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?

For a 7-parameter mutation tool with no annotations and no output schema, the description supplies purpose, undo behavior, a usage example, and validation/clamping edge cases. The main residual gap is per-parameter meaning, especially velocity_scale_per_repeat and transpose_per_repeat units.

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 coverage is 0% across 7 parameters, so the description must compensate. The worked example illustrates track_index, clip_index, cell, cell_length, repeats, and transpose_per_repeat in positional context, but velocity_scale_per_repeat is never mentioned and no parameter's meaning is spelled out, so compensation is only partial.

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?

States a specific verb and resource: 'Repeat one note cell N times instead of sending every note.' It also references the sibling add_notes_to_clip, which helps an agent place it in the tool family. The clip-writing nature is implied rather than stated outright, so it's clear but not maximally sharp.

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 phrase 'instead of sending every note' implies the use case (write repetitive patterns compactly), and add_notes_to_clip is named as the tool whose validation applies. But there is no explicit when-to-use/when-not or a directive comparison against add_notes_to_clip, leaving the agent to infer the routing.

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