Inbetween frames

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the rendering technique and the 'no alpha blur' quality bar, but says nothing about the fact that this mutates the timeline/project, what happens to existing frames, whether the operation is reversible, or what is returned. The schema's insert=false 'replace timeline' semantics is the only signal of destructive behavior and it lives in the schema, not the description.

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?

Two tight, front-loaded sentences with no filler; the technique and constraint come first. The example sentence is marginally redundant with the schema but cheap and concrete.

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?

Scoring note: for an 8-parameter generative tool with no annotations and no output schema, the definition is thin. It omits what the operation does to the timeline, how seed/pattern/durationMs affect output, and any preconditions, leaving an agent to infer behavior from the schema alone.

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 63%; seed, pattern, and durationMs have no descriptions in either schema or prose, and the description does not explain them. The example only restates from/to/steps, which the schema already documents, so it adds almost no semantic value beyond the input schema.

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 and resource (create intermediate frames between two keyframes) plus the distinctive technique (ordered-dither cross dissolve, no alpha blur). It does not explicitly differentiate from ambiguous siblings like sprite_animate, sprite_timing, or sprite_frame, which could also plausibly produce inbetweens.

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?

There is no when-to-use guidance, no prerequisites (e.g. keyframes must exist, palette/project state), and no mention of when to prefer a sibling such as sprite_timing. The trailing 'Example: {from:0,to:2,steps:3}' illustrates parameter form but is not usage guidance.

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