import_ae_comps

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

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It does not disclose where imported comps land (the targetBinPath parameter hints at bins, but the description is silent), what happens on duplicate names, whether the operation is reversible, or whether it is slow/blocking. For an import/mutation tool with zero annotation coverage this is a real gap.

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 or redundancy. It is efficient, though its brevity is also the source of the missing guidance rather than a virtue of tight editing.

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 an import tool with no annotations and no output schema, the description should say what the caller gets back (created project items? comp IDs?) and what preconditions apply. Neither is covered, leaving the agent unable to predict the result of a successful call.

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%: aepPath, compNames (with the 'omit for all' semantics), and targetBinPath are each documented in the schema. The description adds nothing beyond that, 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?

States a specific verb and resource: importing After Effects compositions into 'the project'. Naming 'After Effects compositions' implicitly distinguishes it from sibling import tools like import_media, import_sequences, and import_mogrt. It stops short of explicitly naming those siblings or stating what a 'composition' becomes in the project.

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?

There is no when-to-use guidance, no mention of alternatives, and no prerequisites (e.g. whether the .aep must exist on disk, whether After Effects must be running, whether this overwrites existing comps). An agent must infer the condition that selects this tool over import_media or import_sequences.

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