ae_create_precomp

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

No annotations are provided, so the description carries the full burden. It states the core behavior (precomposing layers into a new comp) but does not disclose what happens to the original layers, whether the operation is reversible, or other side effects. Basic behavior is clear, but deeper transparency is missing.

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 two sentences, front-loaded with the action and benefit. Every word earns its place with no redundancy.

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 complexity (4 parameters, no output schema) and high schema coverage, the description captures the essence but omits important behavioral details such as whether the original layers are replaced by the new precomp, nesting behavior, or typical use steps. It is adequate but not fully complete.

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 75%, so baseline is 3. The description adds minimal extra meaning beyond the schema; it mentions 'apply effects/transforms' which relates to moveAllAttributes, but does not elaborate on parameter details like the purpose of 'name' or 'comp'. The schema already covers parameter descriptions adequately.

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 uses the specific verb 'precompose' and resource 'layers', clearly stating the action of grouping layers into a new composition. It also explains the benefit (keeps organized, apply effects to whole group), which distinguishes it from sibling tools like ae_add_layer_to_comp.

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 implies usage for organizing layers and applying effects/transforms to a group, but does not explicitly state when not to use or compare to alternatives. It gives clear context but no exclusions.

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