add_clip_to_timeline

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing. "Insert edit" hints at ripple behavior to an expert, but the description never states that existing clips are pushed downstream, what happens on failure, or whether the operation requires an open sequence.

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, front-loaded sentence with no filler, so nothing is wasted. The terseness borders on under-specification rather than excess, but structurally it is efficient.

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?

This is a mutation tool with no annotations and no output schema, and the description supplies no behavioral or contextual detail. Even though the parameters are fully documented in the schema, an agent still lacks information on ripple semantics, required preconditions, and error behavior.

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%, including per-field descriptions and an enum for trackType, so the schema already documents all six parameters. The description adds no additional meaning (e.g., how inPoint/outPoint interact with startTime), which is the baseline-3 case.

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 ("Add a project item (clip) to the timeline") and adds an edit mode ("via insert edit") that implicitly distinguishes it from the sibling overwrite_clip_to_timeline. It falls short of a 5 because the insert-vs-overwrite distinction is only implied through jargon rather than stated as a contrast.

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?

There is no explicit when-to-use or when-not-to-use guidance. The description never names overwrite_clip_to_timeline or any other alternative, nor does it state prerequisites such as needing an active sequence or the clip already existing in the project.

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