tween_cel_positions

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

No annotations provided. The description only states it tweens linearly but does not disclose side effects (e.g., overwriting cels, file modification, frame range requirements, or whether it's reversible).

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 followed by a parameter list, which is reasonably concise. However, the parameter list largely duplicates schema information, so it could be more efficiently structured.

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 lacks important context like return values, side effects, or prerequisites. The tool's behavior is not fully explained.

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 lists parameters with titles identical to the schema but adds minimal extra meaning (e.g., 'Starting X position in pixels' is already implied by the parameter name). No explanation of 'create_missing_cels' or 'source_frame_index' beyond their 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 'Tween cel positions linearly across a frame range' with a specific verb and resource. It distinguishes itself from sibling tools like tween_cel_positions_eased by implying linear 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 vs alternatives (e.g., offset_cel_positions, oscillate_cel_positions, or eased variants). No when-to-use or when-not-to-use conditions are stated.

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