resolve_append_to_timeline

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

Adds value beyond annotations (none provided) by stating the import-if-needed behavior and the two-step dry_run/confirm process. Also notes the Live tier restriction. Does not describe error handling or side effects.

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 concise sentences that front-load the purpose and essential workflow instructions. No wasted words.

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?

No output schema, so description should explain what the dry_run plan contains or how to interpret results. It omits return value details, error conditions, and post-confirm behavior. Adequate but with clear gaps.

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%, so parameters are already well-documented. The description adds minimal extra meaning (e.g., 'importing them first if needed' context). Baseline is 3.

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?

Description clearly states the verb 'append clips' to the specific resource 'active timeline', with additional details on importing and the dry_run/confirm workflow. It distinguishes itself from sibling tools like 'assemble_edit' or 'beat_grid' by focusing on timeline appending.

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?

Provides explicit workflow guidance: 'dry_run first, then confirm' and a constraint 'Live tier only'. However, it does not discuss when to use this tool over alternatives like 'assemble_edit' or 'generate_edl'.

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