tween_cel_positions_eased

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

No annotations exist, so the description must disclose behavioral traits. It only states the basic action without detailing consequences like whether existing cels are modified, how easing is applied, or what happens when 'create_missing_cels' is false. The description is insufficient for understanding the tool's behavior.

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 concise sentence, but it is too brief for a tool with 11 parameters. It lacks structure and does not front-load critical details like the easing parameter or required inputs.

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 the complexity (11 parameters, 8 required) and lack of output schema, the description is incomplete. It does not explain return values, side effects, or how this tool interacts with sibling tweens. Agents would lack sufficient context to use it correctly.

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 0%, and the description does not explain any of the 11 parameters. Key parameters like 'easing', 'create_missing_cels', and 'source_frame_index' are not described. The description fails to add meaning beyond the parameter names.

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 clearly states the tool tweens cel positions with easing across a frame range, specifying the action and resource. It differentiates from the sibling tool 'tween_cel_positions' (which likely does linear tweening) by mentioning easing. However, it does not explicitly note the easing parameter or the additional fields like start_x/start_y and end_x/end_y.

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 usage guidance is provided. The description lacks when to use this tool versus alternatives like 'tween_cel_positions' for linear interpolation or 'tween_cel_scale_eased' for scaling. No prerequisites or context are mentioned.

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