overwrite_from_source

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

The description explicitly states that the tool 'replaces existing clips', which is a destructive action. However, the annotation `destructiveHint: false` indicates the opposite, creating a contradiction. This undermines transparency. The description adds behavioral info but contradicts structured data.

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, well-structured sentence that conveys the core functionality without unnecessary words or repetition. It is front-loaded with the key 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?

For a tool with no output schema and two parameters, the description provides the basic outcome (overwrite edit replaces clips) but omits important context: default track behavior, requirement that source monitor is loaded, and playhead position validity. It partially compensates with clarity but lacks completeness for safe 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 100% with both `audio_track_index` and `video_track_index` having descriptions. The tool's description does not add any extra meaning beyond the schema, so it meets the baseline for high 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 the action ('Overwrite the clip from the Source Monitor'), the context ('at the playhead position'), and the effect ('replaces existing clips'). It distinguishes this from sibling tools like 'insert_from_source' by specifying it is an overwrite edit.

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?

The description provides no guidance on when to use this tool versus alternatives like 'insert_from_source', 'replace_clip', or 'overwrite_clip'. It does not mention prerequisites (e.g., source monitor must have a clip open) or conditions for appropriate use.

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