ae_setup_comp

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

Discloses creation of comp with 60fps and motion blur, and returns comp name, but omits that it opens the comp in the viewer (makeActive default true) and other side effects. No annotations to supplement.

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?

Single sentence, no fluff, but could be more structured (e.g., separate key benefits and usage).

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 8 parameters and no output schema or annotations, the description is too minimal, missing many defaults and return behavior beyond 'comp name'.

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?

Only 2 of 8 parameters have descriptions in schema (fps, makeActive). The description adds no parameter details, failing to compensate for low 25% coverage.

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 tool creates a composition with specific settings (60fps, motion blur on) for a 'buttery smooth' look, distinguishing it from sibling tools that add effects or layers.

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?

Implied use for premium motion comps but no explicit when-to-use or when-not-to-use guidance, nor mention of alternatives like ae_create_precomp.

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