set_keyframe_interpolation

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

There are no annotations, so the description bears the full burden of behavioral disclosure. It only restates the operation name and does not reveal whether this mutates existing keyframes, whether it is destructive or reversible, what interpolation modes are supported, or what side effects it may have.

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 short but under-specified rather than genuinely concise. The phrase 'Premiere Pro expanded operation' is filler, and the remaining text is merely the tool name. Every sentence should add value, but this one does not.

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 no annotations, no output schema, and no parameter definitions, the description must provide the full invocation context, but it provides none. An agent cannot determine how to select keyframes, what interpolation values are valid, what the operation does exactly, or how it differs from set_time_interpolation.

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 tool has zero declared parameters, so there are no parameter semantics for the description to clarify. The open schema with additionalProperties: true is not compensated for by the description, but with no formal parameters, the baseline of 4 is appropriate.

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 is essentially a restatement of the tool name: 'set keyframe interpolation.' The prefix 'Premiere Pro expanded operation' adds no semantic content about what the tool actually does. It does not distinguish this from closely related sibling tools like set_time_interpolation or get_keyframes.

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 provided about when to use this tool versus alternatives such as add_keyframe, get_keyframes, remove_keyframe, or set_time_interpolation. There is no mention of prerequisites, such as whether keyframes must be selected, or what kind of interpolation this affects (e.g., spatial vs. temporal).

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