tween_cel_positions

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

No annotations provided, so description bears full burden. It mentions linear interpolation but does not disclose side effects (e.g., file modification, overwriting behavior, or creation of missing cels beyond the create_missing_cels parameter). Lacks detail on what happens to existing cels.

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?

Description is a single sentence followed by a parameter list. No redundant information; each element serves a clear purpose. Efficiently communicates the tool's action and 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?

With 10 parameters, no output schema, and no annotations, the description covers the main action and all parameters. However, it does not specify return values, error conditions, or when the operation might fail (e.g., missing layer). Adequate but not fully comprehensive.

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 adds minimal clarification for each parameter (e.g., 'start_x: Starting X position in pixels'). However, these are largely self-explanatory from parameter names. The descriptions are functional but not enriched beyond basic meaning.

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?

Description clearly states 'Tween cel positions linearly across a frame range', which is a specific verb-resource pair. It distinguishes from siblings like offset_cel_positions (relative offset) and tween_cel_positions_eased (eased 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?

No guidance on when to use this tool vs alternatives. Sibling tools like set_cel_position, offset_cel_positions, and tween_cel_positions_eased are not mentioned, leaving the agent to infer usage context.

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