ae_set_easing

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

No annotations provided, so the description carries the burden. It states it re-eases existing keyframes, implying non-destructive modification, but does not explain scope (all keyframes or selected), side effects, or permissions. Adequate but not thorough.

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?

Single sentence with no redundancy. Front-loaded with the core action and purpose. Every word 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?

Given 5 parameters, no output schema, and no annotations, the description provides the essential purpose and usage context but lacks details on parameters and return behavior. It is minimally complete for a simple tool but could elaborate on the effect of the 'influence' parameter.

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%, and the description adds minimal parameter detail. It mentions 'transform property' and 'preset' but does not explain 'influence' or the exact meaning of each easing preset. Relies heavily on schema enums and defaults.

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 clearly states the verb 're-ease', the resource 'existing keyframes of a transform property', and specifies the presets available. It distinguishes from siblings by focusing on modifying existing keyframes rather than adding new ones.

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 description gives explicit usage context: 'Use after manual keyframing, or to dial in the feel of an already-animated property.' While it doesn't list alternatives, the sibling tools like `ae_animate_transform` imply differentiation. Missing when-not-to-use guidance.

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