add_notes_to_clip

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

With no annotations, the description must carry the burden of disclosing side effects. It indicates a mutation ('Add') but does not explain whether notes are appended to existing ones, whether there is validation, or how errors are handled. This minimal disclosure leaves significant behavioral ambiguity.

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 brief and well-structured: a single-sentence purpose followed by a concise parameter list. Every sentence adds value, and there is no redundancy or 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?

The description covers the core operation and parameter semantics, but omits important context such as whether notes replace or append, time unit expectations, and error conditions. Given the moderate complexity and absence of output schema, the description is adequate but not fully comprehensive.

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 schema provides no descriptions for the parameters, so the description compensates fully by explicitly defining track_index, clip_index, and notes. Particularly, it specifies the note dictionary fields (pitch, start_time, duration, velocity, mute), which is crucial missing meaning beyond the schema's generic array of objects.

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 begins with 'Add MIDI notes to a clip' which is a clear, specific verb plus resource. It clearly distinguishes itself from siblings like create_clip or delete_clip by focusing on note addition rather than clip creation or deletion.

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 provided on when to use this tool versus alternatives, nor any prerequisites such as the clip being a MIDI clip or already existing. The description only states what it does, not the contexts or exclusions.

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