ae_animate_camera

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

With no annotations, description carries full burden. It discloses that keyframes are created and default camera selection. But it omits side effects like whether existing keyframes are replaced, whether a camera is created if missing, or if the tool modifies comp timeline. More behavioral detail would improve transparency.

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?

Two sentences, no wasted words. First sentence defines core function with examples, second specifies default behavior. Well-structured and efficient.

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 9 parameters, no output schema, and no annotations, the description is functional but incomplete. It could mention that keyframes are added to the camera layer's position/pointOfInterest properties, clarify behavior when both position and POI are omitted, and note compatibility with existing keyframes. Lacks details on outcome.

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 56%, so description should add value beyond schema. It explains the overall action and default camera, but does not elaborate on parameters like startTime, endTime, or easing beyond what schema provides. The description adds minimal semantic detail.

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?

Description clearly states the tool animates a camera's position/or point of interest between two 3D points, using terms like 'keyframe', 'dolly/push-in/pan'. It also specifies default behavior with camera name. This distinguishes it from sibling tools like ae_add_camera or ae_animate_transform.

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?

Description implies when to use (to animate camera between points) and provides fallback for unnamed camera. However, it does not explicitly state when not to use this tool versus siblings like ae_animate_transform for camera property animation.

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