ae_animate_mask

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

No annotations provided. The description discloses that the tool sets keyframes on mask expansion or feather over a time range with easing, which is helpful. However, it does not mention potential side effects (e.g., overwriting existing keyframes) or error conditions.

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 sentence with an example conveys the core action efficiently. It is front-loaded with the key operation and has no wasted words.

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?

With 9 parameters and no output schema, the description is too brief. It covers only the essential concept (animating expansion/feather) but omits explanations for common parameters like comp, layer, startTime, endTime, and easing, making it incomplete for effective use.

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 low (11%). The description adds meaning for 'property' (expansion/feather) and 'from/to' values via the example, but does not explain 'comp', 'layer', 'startTime', 'endTime', or 'easing' beyond what the schema provides. It compensates partially but not fully.

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 ('Keyframe') and resource ('mask's expansion or feather') with a practical example. It distinguishes from sibling tools like ae_add_mask and ae_animate_transform by specifying the exact properties animated.

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 implies usage for animating mask properties but provides no explicit when-to-use, when-not-to-use, or alternatives. Sibling tools exist (e.g., ae_animate_transform) but no guidance is given.

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