add_notes_to_clip

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

With no annotations, the description carries the full burden, but it only says 'Add' without clarifying whether notes are appended to existing clip content or replace it. It also omits error conditions, required clip existence, and any destructive potential, which is significant 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 description is short, front-loaded with a clear purpose, and then lists parameters in a clean, scannable format. Every line earns its place with no filler.

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 mutation tool with no annotations, the description is not complete enough: it leaves unclear whether notes are merged or overwritten, and it omits timing/unit semantics needed for correct MIDI note creation. Even though an output schema exists, the invocation semantics are still underspecified.

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 adds useful meaning beyond the raw schema by explaining 1-based indexing and the expected fields inside each note dictionary (pitch, start_time, duration, velocity, mute). However, it does not specify units or value formats for pitch, start_time, duration, or velocity.

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 ('Add') and resource ('MIDI notes to a clip'), clearly stating what the tool does. It is easily distinguishable from sibling tools like clear_notes_from_clip, replace_notes_in_clip, and get_clip_notes.

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?

There is no guidance on when to use this tool versus the sibling note-editing tools. No prerequisites, exclusions, or alternative recommendations are provided, which matters given the many closely related clip operations.

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