ae_setInterpolation

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

Annotations already declare readOnly false, destructive false, openWorld false, so the safety profile is covered. The description adds mode semantics but says nothing about whether changes are reversible on the timeline, whether rounding/keyframe absence causes errors, or what happens with the selection state. With annotations present, a 3 is appropriate.

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 compact parenthetical sentences, front-loaded with the app and the operation. Nearly zero waste, though 'plus roving / auto-bezier / continuous for spatial props' is a bit dense to parse.

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?

It is a non-destructive mutation tool with no output schema and 11 parameters. The description covers targeting and the mode options but omits easyEase and any notion of return/verification, leaving meaningful gaps even for a moderate-complexity write tool.

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 only 18%, but the description compensates well: it maps the mode options (linear|bezier|hold, in/out separately) to inType/outType enums and covers roving, auto-bezier, continuous, keyIndex, time, and 'all keys' targeting. It leaves easyEase completely unexplained, so not a 5.

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 (set keyframe interpolation) and enumerates the interpolation modes, which distinguishes it from siblings like ae_setKeyframe and ae_setKeyframeEase. It does not explicitly name the sibling it differs from, holding it below a 5.

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 clause 'keyIndex, time, or all keys' tells the agent how to target keys, but there is no explicit when-to-use vs when-to-use-alternatively guidance against ae_setKeyframeEase, which is a plausible sibling for a similar task. Usage is implied rather than directed.

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