setKeyframeEase

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that existing ease/influence values on the target keyframes are overwritten, whether the operation is reversible, whether a project/undo state is required, or what the response contains.

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?

One front-loaded sentence with no filler; the verb and target come first. It is short enough that the missing prerequisites are a content gap rather than clutter.

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?

For a 10-parameter mutating tool with zero annotations and no output schema, the description is thin: it says nothing about existing keyframe state being modified, the keyIndex-vs-timeInSeconds alternative, compIndex defaulting to the active comp, or the effect of omitting keyIndex entirely.

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 100%, so the schema already documents all ten parameters with units, ranges, and defaults. The description adds only a partial enumeration of the easeType enum (four of nine values, omitting cinematic/linear/hold) and the notion of custom speed & influence, so baseline 3 is right.

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 ('Apply ease') and resource ('keyframes of a property'), plus names the concrete ease modes. An agent can distinguish it from setLayerKeyframe (which creates keyframes) reasonably well, though no sibling is named explicitly.

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?

Usage is implied by the frame 'apply ease to keyframes' and the description hints that preset ease types and custom speed & influence are two routes. However it never states prerequisites (keyframes must already exist) or when to prefer a preset over custom values, and names no alternative tool.

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