add_notes_to_clip

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

There are no annotations, so the description carries the full burden. It states the tool 'adds' notes, implying non-destructive behavior, but does not disclose whether existing notes are merged, whether notes beyond the clip length are truncated, whether a MIDI clip is required, or any side effects. This is thin for a mutating tool.

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 one-line purpose is front-loaded, followed by a tidy parameter list. No redundant statements, though the parameter explanations are minimal.

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?

The description plus parameter list covers the basic invocation, and an output schema handles return details. However, it omits preconditions (e.g., target clip must be a MIDI clip, not audio), behavior regarding existing notes, and any relationship to sibling operations like clear_notes_from_clip.

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 has no descriptions (0% coverage), but the description defines each parameter and the expected note fields (pitch, start_time, duration, velocity, mute). This meaningfully compensates for the schema gap, though units and valid ranges are not specified.

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 uses a specific verb and resource ('Add MIDI notes to a clip') and is distinguishable from siblings like clear_notes_from_clip. It does not explicitly name siblings, but the action is unambiguous.

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 is given on when to use this tool versus alternatives such as clear_notes_from_clip or create_clip. There are no preconditions, examples, or context about the intended workflow.

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