move_cel

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

With no annotations, the description carries full burden for disclosing behavior. It does not state whether moving a cel overwrites the destination, whether the source cel becomes empty, or what happens if destination already contains a cel. This is a significant gap for a mutating operation.

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 concise sentence that front-loads the core action. No wasted words, and the structure is appropriate for the tool's simple purpose.

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?

The tool involves modifying sprite data, yet the description omits critical context such as destination-cel overwrite behavior, source-cel cleanup, or whether the sprite must be open. With no output schema, the description is incomplete for safe and effective invocation.

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%, and the description does not elaborate on parameter meanings beyond their names. While from_layer/from_frame/to_layer/to_frame are somewhat self-explanatory, the description fails to clarify details like whether frame numbers are zero-indexed or whether layers are referenced by name or ID.

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 uses a specific verb ('Move') and resource ('cel'), and clearly identifies the scope ('from one layer/frame to another'). It unambiguously distinguishes this tool from siblings like clear_cel or set_cel_opacity.

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, nor does it mention prerequisites like having a sprite open or selecting the target layer. There is no context about required states or exclusions.

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