add_notes_to_clip

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

Description discloses destructive nature (replaces entire content) beyond annotation's destructiveHint, details note object structure, and mentions compatibility rationale. No contradiction with annotations.

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?

Two concise sentences plus a structured list for notes format. Front-loaded with main action (REPLACES). Every sentence adds value; no 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?

Covers precondition, note structure, and usage alternatives. With output schema available, return details are handled. Could mention ordering or validation of notes, but overall sufficient for a tool with 3 parameters.

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 coverage is 0%, but description fully documents the complex 'notes' parameter with pitch range, time units, velocity range, and mute boolean. For 'clip_index' and 'track_index', minimal addition, but context from sibling tools 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?

Description states verb 'REPLACES' entire note content, specifies name is for upstream compatibility, and contrasts with sibling 'edit_notes' for partial updates. Clearly identifies tool's core function and distinguishes it.

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?

Explicitly instructs to use 'edit_notes' for adding/removing a subset, states precondition that clip must exist, and implies this tool is for full replacement. Provides clear when-to-use and when-not-to-use guidance.

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