import_ae_comps

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

With no annotations, the description carries full behavioral burden, yet it only implies a write operation. It never says where imported comps land (related to targetBinPath), whether a live Dynamic Link dependency is created versus a baked import, whether AE must be running, or whether the operation is reversible.

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 short, front-loaded sentence with no filler. It is efficient, though the brevity reflects under-specification rather than disciplined density.

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 mutation-style import tool with no annotations, no output schema, and an undocumented required path parameter, the description does not provide enough for an agent to call it confidently. Prerequisites, destination behavior, and result shape are all absent.

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?

The description explains none of the three parameters. compNames and targetBinPath are well documented in the schema, but the required aepPath has no description anywhere, leaving a real gap in the one parameter an agent must supply.

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 ('Import compositions from an After Effects project') and the Dynamic Link mechanism, which implicitly separates it from generic siblings like import_media or import_sequences. It does not explicitly name those alternatives, so it stops short of a 5.

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 guidance on when to use this instead of import_media/import_sequences, nor on prerequisites such as After Effects being installed and the project being available for Dynamic Link. The parenthetical hints at a dependency but never states it as a condition.

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