Apply Easy Ease easing to all keyframes of a property in After Effects, selecting ease-in, ease-out, or both to control motion smoothness.
Apply Easy Ease to all keyframes of a property (smooth in/out easing)
| Name | Required | Description | Default |
|---|---|---|---|
| comp_name | Yes | Composition name | |
| ease_type | No | Which side(s) to apply easing to | ease_in_out |
| layer_name | Yes | Layer name | |
| property_path | Yes | Property path |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the core effect (smoothing all keyframes) but omits material side effects: it overwrites any existing per-keyframe interpolation on the property, and behavior when the property has no keyframes is unstated.
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?
A single 13-word sentence, front-loaded with the action and ending with a useful jargon-defining parenthetical. Every word earns its place with zero waste.
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?
Adequate for a simple batch operation with fully documented parameters, but gaps remain: no output schema or stated return value, no indication of behavior when the property has no keyframes, and no error/no-op semantics.
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 description coverage is 100%, so the schema already documents all four parameters, including the ease_type enum with its options. The description adds only the 'all keyframes of a property' context; baseline 3 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?
States a specific verb and resource: applies Easy Ease to all keyframes of a property, with the parenthetical defining the AE jargon term. The batch 'all keyframes' scope distinguishes it from per-keyframe siblings like ae_set_keyframe_interpolation.
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?
Usage context is implied: this is the one-shot standard-easing convenience operation. However, it never names alternatives or states when not to use it, such as when per-keyframe interpolation control via ae_set_keyframe_interpolation is required.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.