add_notes_to_clip

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

The description confirms the destructive nature (replace entire notes) which aligns with the destructiveHint annotation. It adds behavioral context beyond annotations by specifying the operation replaces all notes.

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 efficient sentences: purpose, alternative, parameter format and precondition. No fluff, front-loaded with action.

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 output schema exists and the tool's simplicity, the description covers purpose, parameter details, precondition, and alternative. No gaps.

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 coverage, the description adds significant meaning for the 'notes' parameter by detailing its structure (pitch, start_time, etc.). However, 'clip_index' and 'track_index' lack additional semantics beyond their names.

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 'REPLACES the clip's entire note content', providing a specific verb and resource. It distinguishes itself from the sibling 'edit_notes' by contrasting replacement vs. subset modification.

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 contrasts with 'edit_notes' for subset operations, and includes a precondition (clip must exist). This gives 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.