ae_add_layer_to_comp

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the basic action and does not mention side effects (e.g., layer ordering, changes to source items), error conditions (e.g., source not found), or any required permissions. This is insufficient for a mutation tool.

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?

The description is a single concise sentence of 14 words. It is front-loaded with the key action and resource, contains no superfluous words, and is immediately understandable.

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 the tool's simplicity (3 parameters, no output schema), the description is minimally adequate but lacks details on the outcome of the operation (e.g., does it return a layer reference? How is the layer inserted?). The schema fills some gaps, but overall completeness is average.

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 coverage is 100% with all parameters described. The description adds no additional context beyond what the schema provides. It does not explain defaults (e.g., targetComp defaults to active comp), behavior when omitted, or formatting hints for the position array. Baseline 3 is appropriate.

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 action: adding an existing composition or footage item as a layer into another composition. The verb 'Add' and resource 'layer to a comp' are specific, and the inclusion of 'existing composition' and 'imported footage' helps differentiate from other add tools like 'ae_add_adjustment_layer'.

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?

The description provides no explicit guidance on when to use this tool versus alternatives (e.g., ae_add_effect, ae_create_precomp). There is no mention of prerequisites, contexts, or when not to use it. The usage is only implied by the action itself.

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