keyframe_clip_saturation

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

With no annotations, the description carries the transparency burden. It discloses the core behavior (gradual transition across frames via a BezierSpline), which adds value. However, it does not state whether existing keyframes are overwritten, whether it mutates the clip in place, or what limitations apply.

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 one efficient sentence with no filler. The core action is front-loaded, the example is useful, and every clause earns its place.

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 mutation tool with five parameters and no annotations, the description is thin. It lacks usage context, does not clarify the meaning of a null end_frame, and gives no indication of side effects on existing animation. The output schema exists but is not shown, so the description still needs to cover the invocation essentials more completely.

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%, so the description must compensate. It does add meaning by illustrating start and end saturation values (1.0 to 0.0) and the notion of 'across frames', which maps to start_frame/end_frame. But it does not explain item_id, the null end_frame default, or frame units/behavior.

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 states a specific verb ('Animate'), a clear resource (clip color/saturation), and a concrete method ('Fusion BezierSpline on the clip'). The example '1.0 full color to 0.0 black and white' makes the saturation focus obvious, though it does not explicitly name or contrast sibling tools like animate_color_fx.

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 guidance is given for when to use this tool versus alternatives. The description only says what it does; it does not mention prerequisites, when-not-to-use, or distinguish itself from related tools such as set_clip_grade or animate_color_fx.

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