add_to_timeline

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the core action and does not mention side effects, whether the operation is destructive, required permissions, or what happens to existing timeline content. The schema's insertMode parameter hints at behavior, but the description itself lacks transparency.

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, concise sentence that front-loads the key information (source, destination, and placement specifics). It contains no fluff or repetition.

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?

The schema is rich and covers all parameter semantics, but the description itself is minimal. It lacks usage guidance and behavioral context for a complex timeline-editing operation. However, the overall definition (description + schema) is moderately complete, justifying a mid-level score.

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 detailed explanations for each parameter (e.g., linkAudio's purpose, sourceInPoint/OutPoint semantics). The tool description adds no parameter meaning beyond the schema, so a baseline of 3 is appropriate.

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 specific action: adding a media clip from the project panel to a sequence timeline at a specific track and time. This distinguishes it from siblings like insert_from_source (source monitor) and add_to_timeline_batch (batch operation).

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 or overwrite_from_source. It also does not mention prerequisites or when not to use it, leaving the agent to infer the use case solely from the tool name and context.

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