ae_setEffectKeyframe

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

Annotations already declare this is a non-readOnly, non-destructive, closed-world mutation, so the safety profile is covered. The description adds the useful detail that it keys one parameter per call and what ease/interpolation mean, but omits important behavior: what happens if a keyframe already exists at that time, whether time is seconds or frames, and whether the effect must pre-exist.

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?

A single compact sentence with the tool's domain and scope front-loaded and no filler. Its brevity is effective, though it leans on the parenthetical to do heavy lifting.

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 5-required-parameter mutation with no output schema and low schema coverage, the description is only partially sufficient. An agent can call it, but must guess time units, how effect/property are addressed, and the return/feedback shape.

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 25% across 8 parameters, so the description should carry more weight. It does clarify 'ease influence %' and lists the interpolation modes (linear|bezier|hold), which is genuine value, but layer/effect/property/time/value and the units of time remain unexplained beyond the minimal schema text.

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 (keyframe) and resource (an effect parameter in After Effects), and the phrase 'one effect parameter at a time' narrows the scope relative to broader keyframe siblings. It does not name ae_setKeyframe/ae_setKeyframes explicitly, so an agent still has to infer the boundary.

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 parenthetical hints at when the optional ease/interpolation arguments matter, and 'one effect parameter at a time' implies the alternative is a bulk/loop approach. But there is no explicit when-to-use vs ae_setKeyframe, ae_setKeyframes, ae_setKeyframeEase or ae_setInterpolation, and no prerequisites (e.g. effect must already exist on the layer).

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