tween_cel_positions

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the linear interpolation across frames but does not clarify side effects like overwriting existing positions, whether it modifies the sprite in-place, or any prerequisites. It is adequate but not thorough.

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 front-loaded with a one-line purpose, followed by a structured parameter list. It is informative without being overly verbose, though the bullet list could be slightly more compact. No wasted sentences.

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 (10 parameters) and lack of output schema or annotations, the description covers inputs well but misses behavioral context like whether it modifies the sprite directly, what happens to existing cels, or error conditions. It is not fully complete for an agent to understand all implications.

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%, so the description fully compensates by explaining all 10 parameters in the Args section with clear meanings (e.g., 'start_frame: Starting frame index (1-based)'). This adds significant value beyond schema titles.

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 explicitly states the verb 'tween' and the resource 'cel positions' with the qualifier 'linearly across a frame range', making the purpose clear. However, it does not differentiate from sibling 'tween_cel_positions_eased', which performs a similar tween with easing, so it loses a point for lacking sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'tween_cel_positions_eased' or 'offset_cel_positions'. It only states the action without explaining context or exclusions, leaving the agent to infer usage.

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