Add clips to the open scene

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

Annotations already indicate this is a write operation (readOnlyHint=false) with possible side effects. The description adds key behavioral details: the operation is free, maintains order, and does not invoke the costly Extend feature. These go beyond what annotations provide.

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 two sentences, front-loaded with the essential action, and every sentence adds value. There is no redundancy or unnecessary 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 one-parameter tool with annotations, the description is fairly complete. It explains the action, cost, and a key distinction from Extend. It implicitly assumes an open scene, which is clear from the title and first sentence. Missing details like error handling are not critical given the 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?

The input schema covers 100% of the parameter, describing it as 'Clip media ids, in the order they should appear'. The description reinforces this by stating 'in order' and specifying the source as 'library clips', adding slight additional semantic value.

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 ('Add') and resource ('library clips' to 'open scene'), clearly stating what the tool does. It also distinguishes from the sibling 'Extend' feature, which is mentioned explicitly.

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 context on when to use the tool (adding clips in order to the current scene) and explicitly states that it does not use the Extend feature, which has a cost. However, it does not compare with other sibling tools like flow_create_scene or flow_export_scene.

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