timeline_create

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

The description discloses one side effect: 'The new timeline becomes current.' However, it omits other behavioral details such as prerequisites (e.g., open project), error handling, or overwrite behavior. Since no annotations are provided, the description carries the full burden, and it only partially addresses 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 composed of three concise sentences that immediately state the purpose and key usage details. Every sentence adds value without redundancy, demonstrating efficient structure.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description covers core aspects: creation modes and a side effect. It lacks prerequisites and return value, but these are somewhat implied by the tool's nature. The completeness is good relative to context.

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?

With 0% schema description coverage, the description adds meaning by explaining the 'clips' parameter accepts clip handles from specific tools. However, it does not detail the format of the handles or explain the 'name' parameter beyond being required. It provides some semantic value but is incomplete.

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 creates a timeline, with two explicit modes (empty or populated from clips). It distinguishes itself from siblings like timeline_duplicate and timeline_delete by focusing on creation and population via clip handles.

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 clear guidance on when to use: to create a new timeline, optionally populating it with clips using handles from media_import or clip_list. While it does not explicitly list when-not scenarios, the sibling context and the mention of 'empty or populated' imply exclusions.

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