Write MIDI notes into an existing clip, optionally clearing it first with replace; notes beyond the clip length are kept for when the loop is extended.
Write MIDI notes into an existing clip. replace=True clears the clip first. Notes beyond the clip length are kept but won't play until the loop is extended.
| Name | Required | Description | Default |
|---|---|---|---|
| notes | Yes | ||
| replace | No | ||
| slot_index | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden and does real work: it discloses that replace=True destroys existing clip contents and that notes beyond clip length are retained but silent until the loop is extended. These are non-obvious mutation side effects an agent would otherwise miss. It does not cover permissions or the coordinates needed to target the clip.
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?
Three short sentences, front-loaded with the primary action, then the replace caveat, then the loop-length edge case. No filler and every sentence earns its place.
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 and no output schema, it covers the destructive replace path and the beyond-length behavior well. However, it omits how track_index/slot_index identify the target clip, which is essential context an agent needs to invoke it correctly.
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?
Top-level schema coverage is 0%: track_index, slot_index, and notes have no descriptions, and the description only explains replace=True. The nested Note fields carry their own schema descriptions, but the description does not compensate for the undocumented top-level parameters, leaving the clip-targeting coordinates unexplained.
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?
States a specific verb and resource: 'Write MIDI notes into an existing clip.' The word 'existing' tells the agent a clip must already be present, implicitly distinguishing it from create_clip. It stops short of explicitly naming sibling alternatives, but the core purpose 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?
There is no explicit when-to-use guidance or comparison against siblings like create_clip, set_clip, or remove_notes. The only usage-adjacent content is the replace parameter behavior, which is a mechanic rather than a routing rule. An agent must infer the appropriate context itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.