set_keyframe_interpolation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists the interpolation modes and scope but does not explain what mutation occurs, whether changes are reversible, what happens when 'all' is used, or whether existing keyframe values are preserved.

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, front-loaded sentence with no wasted words. It efficiently conveys the action, accepted interpolation values, and scope. It is terse but appropriately so for a focused mutation tool.

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 seven required parameters, no annotations, and no output schema, the description is too thin for the tool's complexity. It does not explain keyframe identification ({index} vs {time}), effect/property lookup, or error behavior for invalid tracks or missing keyframes.

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 71%, so the schema already documents most parameters, including the keyframe selector and interpolation enum. The description adds marginal value by clarifying that interpolation applies to 'one keyframe or all' and by naming the supported modes, but it does not explain effect/property resolution or track indexing 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 states a specific verb and resource ('Set keyframe interpolation') and names the supported interpolation modes. It also clarifies the scope ('for one keyframe or all'), which distinguishes it from sibling tools like add_keyframe or remove_keyframe. It does not explicitly name those siblings, but the purpose is unambiguous.

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 phrase 'for one keyframe or all' gives an implicit usage rule for scoping the operation, which is helpful. However, there is no guidance on prerequisites (e.g., keyframes must already exist), when to prefer this over set_effect_property, or what to do with the required effect/property selectors.

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