ae_create_composition

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only names the action and context; it does not disclose what happens when no project is open, whether the new composition becomes active/selected, whether the operation is reversible, or any error behavior. The description adds little beyond what the tool name already conveys.

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 11-word sentence that front-loads the action and resource with zero wasted words. 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?

For a creation tool with no annotations, no output schema, and 6 parameters, the description is too thin. It omits prerequisites (an open project), expected side effects, failure conditions, and the existence of the sibling ae_batch_create_compositions for multi-comp creation. An agent cannot anticipate what happens when it invokes this tool.

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 100%, with all 6 parameters (name, width, height, duration, frame_rate, pixel_aspect) already documented in the input schema. The description contributes no parameter-level information, so the baseline of 3 applies.

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 states a specific verb ('Create'), resource ('a new composition'), and scope ('in the current After Effects project'). The word 'new' plus the verb 'create' conceptually distinguishes it from nearby siblings like ae_duplicate_composition, ae_modify_composition, and ae_delete_composition, though it does not explicitly name any of them.

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?

No guidance is given on when to use this tool versus the many related siblings: ae_batch_create_compositions (bulk creation), ae_duplicate_composition (copying an existing comp), or ae_modify_composition (altering an existing comp's settings). The phrase 'current project' implies a prerequisite of an open project but never states it.

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