offset_cel_positions

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

No annotations are provided, so the description bears full burden. It describes the action but does not disclose behavioral traits such as in-place modification, destruttiva nature, prerequisites (cel existence), return values, or error conditions. For a mutation tool, this is a significant gap.

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 concise: a one-sentence action statement followed by a parameter list. It is front-loaded with the purpose and efficient in its layout. No unnecessary text.

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 6 required parameters, no annotations, and no output schema, the description is adequate but incomplete. It covers the core action and parameters but lacks behavioral details, error handling, and prerequisites. It is minimally viable.

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?

With 0% schema description coverage, the description compensates by explaining all six parameters: filename, layer_name, start_frame (1-based), end_frame (inclusive), dx, dy. This adds meaning beyond the schema's titles. However, it lacks constraints like valid ranges or that dx/dy can be negative.

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 tool offsets cel positions by a delta across a frame range. The verb 'offset' is specific, and the resource 'cel positions' is explicit. It distinguishes itself from siblings like set_cel_position (absolute) and tween_cel_positions (animated).

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 lists parameters but does not explicitly state when to use this tool versus alternatives like set_cel_position or tween_cel_positions. Usage is implied for shifting cels by a constant delta, but no guidance on exclusions or when not to use.

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