Opentoonz Set Cells

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

With no annotations, the description carries the full burden. It does disclose a meaningful precondition (levels must exist) and implies overwrite semantics via 'replace', but says nothing about what happens to pre-existing xsheet content at those rows, error behavior for a missing level, or required authorization.

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?

Three short sentences, zero filler, and the core operation is front-loaded before the placement schema and the routing note.

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?

An output schema exists, so return values need no prose, and the description covers the operation, the placement record shape, and the level precondition. Remaining gaps are minor: no explicit statement about overwriting existing cells or failure modes when a level or scene is missing.

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 placements array items are untyped objects (additionalProperties: true), so the description is the only source for the placement shape. It documents row/col/level/fid with types, which is substantial added value; only workspace/scene remain unexplained, though they are self-evident from siblings.

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?

States a specific verb+resource ('Place/replace cells on a scene's xsheet') and names both a sibling to use instead (opentoonz_exposure) and one whose output it depends on (opentoonz_import_images_as_level). An agent can distinguish it from the other opentoonz_* tools without opening the schema.

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?

Gives an explicit conditional alternative: for the common 'hold each drawing for N frames' task, use opentoonz_exposure rather than computing rows manually. It also states the prerequisite that levels must already exist, pointing to the tool that creates them.

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