ae_setKeyframe

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

Annotations already declare a non-read-only, non-destructive, non-open-world mutation, so the safety profile is covered. The description adds that ease influence, interpolation, and easeIn/easeOut are optional, but says nothing about whether an existing keyframe at the same time is overwritten, whether the layer must be selected, or how errors surface.

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 front-loaded sentence with no filler, stating the operation first and the optional modifiers after. It is dense but well ordered; a semicolon-delimited breakdown of the optional knobs would be marginally clearer.

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 9-parameter mutation with no output schema and thin schema descriptions, the definition covers the conceptual knobs but omits time-unit conventions and overwrite semantics, which matter most for correct invocation. It is minimally adequate rather than complete.

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 22%, so the description must carry weight; it does partially compensate by explaining 'property (aliases or path)', 'ease influence %', 'interpolation', and 'easeIn/easeOut'. However, it leaves critical ambiguities unresolved — the units of 'time' (seconds vs. frames) and 'ease', and what value types are acceptable for a property.

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?

Specific verb + resource: 'set one keyframe on any property ... at time with value', and it names the accepted property addressing forms (aliases or path). It is clearly a single-keyframe write, though it does not explicitly distinguish itself from close siblings like ae_setKeyframes, ae_setKeyframeEase, or ae_setInterpolation.

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?

Use is only implied by 'set one keyframe' versus the plural ae_setKeyframes sibling; there is no explicit statement of when to use this instead of ae_setKeyframeEase or ae_setInterpolation, nor prerequisites (comp context, layer selection). The agent must infer routing from tool names alone.

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