timeline_append_clips

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

With no annotations, the description carries the behavioral transparency burden. It discloses that clips are searched in the media pool's current folder and appended in order—behavior beyond the basic schema. It does not detail edge cases like missing clips, but the additive nature of the operation reduces the need for destructive warnings.

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?

Two sentences with no wasted words: the first states the action, the second clarifies search and ordering behavior. The structure is front-loaded and 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 simple one-parameter tool with an output schema. The description explains the core operation, search location, and ordering. It could mention what happens when no matching clips are found, but the description is largely complete for its complexity.

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 fully describes clip_names with 'List of clip names (as shown in the media pool)'. The description only reiterates that clips are matched by name, adding no new parameter-level detail. Baseline of 3 applies because schema coverage is 100%.

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 uses a specific verb ('Append') and clear resources ('media pool clips' to 'the end of the current timeline'), making the action unambiguous. It distinguishes itself from sibling tools like timeline_create_timeline_from_clips and timeline_delete_clips.

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?

It clearly states it appends to the current timeline, which is useful context for when to use this tool. It also explains the search scope (current folder), hinting at a prerequisite. However, it does not explicitly name alternatives or exclusion criteria, so it does not reach the top score.

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