timeline_append

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

The description discloses that clip_ranges optionally trims clips and explains the structure, which is useful. However, it omits behavioral details like what happens if the timeline doesn't exist, if clips are invalid, or any side effects. No annotations exist to compensate.

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 concise with two sentences. First sentence states the core action, second explains the optional parameter. No redundant information.

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 simple append tool, the description covers the essential functionality and parameter details. It could mention return value or prerequisites (e.g., timeline must exist), but overall it is fairly complete given the tool's simplicity.

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?

The input schema has 0% description coverage, so the description must compensate. It explains clip_ranges fields (startFrame, endFrame, recordFrame, trackIndex, mediaType) and notes that clips are from the media pool, but does not clarify what the strings in 'clips' represent (IDs, names?). Partial compensation.

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 tool appends media pool clips to the end of the current timeline, using a specific verb and resource. It distinguishes from siblings like timeline_create or timeline_import which deal with entire timelines.

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?

No guidance is provided on when to use this tool versus alternatives such as timeline_create or clip_replace. It does not mention prerequisites, limitations, or when not to use it.

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