add_notes_to_clip

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

The description discloses critical behavioral traits: default replacement of all existing notes, append mode to keep existing notes, default velocity and mute values, and the required note structure. Since no annotations are provided, the description fully covers behavioral disclosure.

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 (4 lines) and well-structured, using a bullet-like list for note keys. 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?

The description covers input parameters and behavior adequately. It does not explicitly state that the tool applies to session clips (vs. arrangement clips), but the sibling tools and context imply it. Given the presence of an output schema, return value explanation is unnecessary.

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 significant meaning beyond the schema: it details the keys of the notes dict (pitch, start_time, duration, velocity, mute) with ranges and defaults, explains the append parameter's effect, and provides usage context. Schema coverage is 0%, so the description fully compensates.

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 'Add MIDI notes to a clip' with specific verb and resource. It distinguishes from siblings like get_clip_notes and set_arrangement_clip_notes by focusing on adding 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?

It explains the two modes (replace by default vs. append=true) and the default behavior, giving clear guidance on when to use each. No explicit alternatives are listed, but the context is sufficient.

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