add_notes_to_clip

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

No annotations are provided, so the description carries the transparency burden. It explains the snap_to_scale behavior and key override, but it does not disclose whether notes are merged with existing notes, what happens if the clip does not exist, or the return value.

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 front-loaded with a one-sentence purpose followed by a clean parameter list. While slightly verbose, every parameter entry provides necessary information that the schema lacks.

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 all parameters and special behavior, but misses important operational context such as whether existing notes are preserved, error handling for missing clips, and return behavior. Given no annotations and no output schema, these gaps 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?

With 0% schema description coverage, the description fully documents all six parameters, including the internal fields of 'notes' and the default behavior of 'key' and 'snap_to_scale'. This adds significant semantic value beyond the bare schema.

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 'Add MIDI notes to a clip' uses a specific verb and resource, making the tool's purpose immediately clear. It naturally distinguishes itself from siblings like get_clip_notes and create_clip by focusing on adding notes to an existing clip.

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 explicit when-to-use or alternative guidance, but the description and name imply the tool is for adding MIDI notes to an existing clip. This is sufficient for a straightforward operation, though it does not mention exclusions or prerequisites.

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