tween_cel_scale_eased

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

No annotations provided. The description does not disclose behavioral traits such as whether it modifies existing cels, creates new ones, or its destructive nature (hinted by 'replace' parameter). Lacks detail on side effects or required permissions.

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 it is too brief for the tool's complexity. While it has no filler, it lacks structure and misses opportunities to front-load key information.

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 tool's 11 parameters, 6 required, and no output schema, the description is severely incomplete. It does not explain the concept of tweening, how easing works, or the expected outcome. The description fails to provide enough context for effective tool selection.

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%; the description adds no meaning beyond the parameter names. None of the 11 parameters (e.g., start_scale, easing, anchor) are explained. The description does not clarify their purpose or acceptable values.

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 action (tween), the resource (cel scale), and the context (with easing across a frame range). It effectively distinguishes from sibling tools like 'tween_cel_positions_eased' which tweens positions.

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 on when to use this tool versus alternatives. With many tween tools (scale, opacity, positions), the description should indicate when scaling is appropriate. No prerequisites or exclusions are mentioned.

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