propagate_cels

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states the action but does not reveal side effects (e.g., overwriting cels, required frame existence) or prerequisites (e.g., layers must exist). The 'replace' parameter is mentioned but not explained in context.

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: one sentence for purpose, followed by structured parameter documentation. No redundant or extraneous 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?

The description covers the core functionality and parameters well. However, it does not mention what happens if target frames do not exist, or how this tool compares to similar siblings like 'propagate_frame_to_range'. Still, it is largely sufficient for usage.

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%, but the description includes an 'Args' section that documents each parameter's meaning, including that frame indices are 1-based and that 'replace' defaults to True. This fully compensates for the lack of schema descriptions.

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 action ('Copy cels'), the source ('from a source frame'), the destination ('to a range of frames'), and the target ('for specific layers'). It distinguishes from siblings like 'copy_cel' and 'propagate_frame_to_range' by specifying per-layer copying across a range.

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?

No explicit when-to-use or when-not-to-use guidance is provided. Siblings like 'copy_cel', 'duplicate_frame_range', and 'propagate_frame_to_range' exist, but the description does not differentiate scenarios or mention alternatives.

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