set_time_interpolation

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

With no annotations, the description carries the full burden of disclosing side effects, target object, and mutation behavior. It only restates the operation name and provides no detail about what changes, whether it is reversible, or what state it requires.

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 very short and front-loaded with the operation name. The phrase 'expanded operation' is boilerplate filler, but the overall structure is lean and readable.

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?

This is a mutating setter with no annotations, no output schema, and no parameter guidance. The description does not state which object it operates on, what time-interpolation values are expected, or what context must be prepared, leaving the invocation conditions underspecified.

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?

There are zero declared parameters, so the schema leaves nothing to document and the 0-param baseline applies. However, additionalProperties is true, so arbitrary arguments could be accepted, and the description gives no hint about what those might be.

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 names a specific operation and resource: 'set time interpolation' in Premiere Pro. It is clear in isolation but does not differentiate from closely related siblings such as set_keyframe_interpolation or set_frame_blend, and 'expanded operation' adds little semantic value.

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 is given about when to use this tool instead of related interpolation tools, nor any prerequisites such as a selected clip, active sequence, or keyframe context. The agent must infer usage entirely from the tool name.

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