set_time_interpolation

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

No annotations are provided, so the description must disclose behavioral traits. It only states the operation is a setter (mutation) without detailing side effects, permissions, or undo behavior. The mention of 'Uses QE DOM' adds minimal practical insight.

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, efficient sentence that front-loads the action. It contains no unnecessary words or repetition, making it easy to parse quickly.

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 no output schema or annotations, the description is somewhat incomplete. It does not mention return values, error conditions, or prerequisites (e.g., clip must be in a sequence). For a simple setter, this may suffice, but more context would be beneficial.

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 coverage is 100%, so baseline is 3. The description adds the list of interpolation types, but the schema already provides the same information in the parameter description (0=Frame Sampling, etc.). No additional semantic value beyond the schema.

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 action: 'Set time interpolation type for a clip', lists the three specific types (Frame Sampling, Frame Blending, Optical Flow), and distinguishes it from siblings like set_keyframe_interpolation by mentioning 'time interpolation' and 'QE DOM'.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., set_keyframe_interpolation). The description does not specify prerequisites like whether the clip must be on a timeline or if the tool is applicable only to video clips.

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