set_time_interpolation

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

The description states 'Set time interpolation type' indicating a write operation (consistent with readOnlyHint=false), but adds no behavioral details beyond the schema. It mentions 'Uses QE DOM' which hints at internal mechanics but does not disclose side effects, reversibility, or required clip state.

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 covers the core purpose. It could be slightly improved with structured formatting (e.g., bullet list) but is not verbose.

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?

With 2 simple parameters and no output schema, the description provides the basic purpose but lacks context on the meaning of interpolation types, typical use cases, or whether the operation is reversible. Adequate but incomplete for unfamiliar users.

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% with clear descriptions for both parameters. The description's parenthetical list of values is redundant with the schema. No additional parameter semantics provided.

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) and lists the three options (Frame Sampling, Frame Blending, Optical Flow), distinguishing it from sibling tools like set_frame_blend which likely sets a single type flag.

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 guidance on when to use this tool versus alternatives such as set_frame_blend or other clip property setters. No mention of prerequisites, when not to use, or typical scenarios.

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