tween_cel_positions_eased

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

With no annotations, the description must disclose side effects and behavior. It does not explain what happens to existing cels, whether missing cels are created (though schema has a parameter), or what the source_frame_index does. The description is insufficient.

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 sentence, which is concise but lacks structure and front-loading of critical information. It is appropriately short but under-specified.

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 11 parameters, 8 required, and no output schema, the description should provide more context about the tweening process, easing options (e.g., 'smoothstep' is default but not mentioned), and how it relates to siblings. It is incomplete for the complexity.

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 0%, so description should explain parameters, but it only states the overall action. It adds no meaning beyond the schema titles, which are already fairly clear. Key parameters like easing (with default 'smoothstep') are not elaborated.

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 specifies the verb 'tween' and resource 'cel positions', and mentions easing and frame range, making the purpose clear. However, it does not distinguish itself from the sibling tool 'tween_cel_positions' which likely does the same without easing.

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 on when to use this tool versus alternatives like 'tween_cel_positions' or 'offset_cel_positions'. There is no mention of prerequisites or when not to use it.

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