live_clip_update_notes

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'update existing MIDI notes' but does not describe mutation behavior (e.g., partial vs full replace), side effects, or required permissions. The tool modifies state but the description gives no details on what happens to other properties not specified.

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 a single sentence with no redundancy. It is front-loaded and efficient, but could benefit from more detail without becoming verbose.

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?

Given the complex nested input schema (ref object, updates array with many optional fields), no output schema, and no annotations, the description is incomplete. It does not explain the workflow, how the updates array interacts with existing notes, or what success looks like. More context is needed for proper usage.

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?

Schema description coverage is only 25% (only timeout has a description). The description provides no additional meaning for parameters like ref or updates. It does not explain that note_id is required in each update item or what the fields represent. Description fails to compensate for the low schema coverage.

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 it updates existing MIDI notes by note_id, which is a specific verb and resource. However, it does not differentiate from sibling tools like live_clip_add_notes (adds new notes) or live_clip_notes (gets notes), but the purpose is clear enough.

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 on when to use this tool versus alternatives such as live_clip_add_notes. No context about prerequisites, limitations, or conditions under which updates are appropriate.

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