set_cel_position

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

No annotations provided; description mentions create_if_missing and source_frame_index parameters, which add some behavioral context, but lacks details on side effects like file modification or overwriting behavior.

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 clear docstring with an Args list, but could be slightly more concise; still well-structured and front-loaded.

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 no output schema or annotations, the description adequately explains the tool's function and parameters, but does not clarify return value or whether changes are permanent.

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 provides full parameter meanings via the Args list, which adds essential context beyond the schema's titles and types.

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 'Set a cel's position in a specific layer and frame' with a specific verb and resource, distinguishing it from sibling tools like offset_cel_positions or tween_cel_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?

The description implies usage for setting a single cel's position but does not explicitly state when to use or avoid it compared to alternatives like move_region or offset_cel_positions.

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