overwrite_clip

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: existing material at that time is replaced. However, it does not say the extent of the destruction (does it trim/split or fully delete overlapped clips, across one track or all?), whether it is undoable, or what is returned. Meaningful but incomplete disclosure for a destructive mutation.

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?

A single short clause with the defining behavior front-loaded after the label; no filler. Slightly clipped to the point of being ambiguous ('place media at a time'), which is under-specification rather than verbosity.

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?

Six parameters, no annotations, no output schema, and a destructive operation — the description should go further about the replacement semantics. It is minimally adequate because the schema is fully documented, but an agent still can't predict exactly which clips get altered or how to verify the result.

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%, covering time, nodeId, sourceIn/Out, trackType defaulting to video, and trackIndex. The description adds only the phrase 'at a time', which restates the schema's time parameter and adds no format or edge-case guidance beyond structured data. Baseline 3 applies.

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 ('Overwrite edit: place media at a time') and adds the distinguishing trait 'replacing whatever is there', which separates it from insert-style placement. It stops short of naming the sibling (insert_clip/append_clip) it contrasts with, so the differentiation is inferential rather than explicit.

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?

Implies the usage context (overwrite mode, when you want existing material replaced) but never states when to prefer it over insert_clip or append_clip, nor any prerequisites such as an active sequence or targeted track. The agent must infer the choice from the word 'overwrite'.

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