ae_set_keyframe_interpolation

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the action without explaining side effects, whether an existing keyframe is required, how in/out interpolation types interact, or what happens if the keyframe index is invalid. The mutating nature is implied by 'Set' but not elaborated.

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 short sentence with no filler words, and the parenthetical '(easing)' adds helpful clarity. It is front-loaded and easy to parse, though slightly sparse for a tool with six parameters.

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 annotations, no output schema, and a mutating operation, the description is incomplete. It does not explain what success looks like, whether the keyframe must already exist, or how this relates to nearby sibling tools like ae_easy_ease_keyframes and ae_add_keyframe. More operational context is needed for an agent to invoke this confidently.

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 the schema already documents all six parameters, including the in_type and out_type enums and the 1-based keyframe_index. The description adds no extra parameter meaning, so the baseline score of 3 applies; it does not clarify ambiguous values like 'auto' versus 'auto_bezier'.

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 ('Set'), resource ('interpolation type (easing)'), and target ('a keyframe'), which is clear enough to understand what the tool does. It does not explicitly differentiate it from sibling tools like ae_easy_ease_keyframes, but the keyframe-specific focus helps distinguish it from add/get/delete keyframe tools.

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 description provides no guidance on when to use this tool versus ae_easy_ease_keyframes, ae_add_keyframe, or ae_set_layer_property. There is no mention of prerequisites, such as the keyframe already existing, or any indication of when this approach is preferred over alternatives.

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