ae_create_layer

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 usefully discloses 'One undo step' and the default center justification, but omits permissions/auth needs, what happens if no active comp exists, and how the created layer is returned or identified.

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?

Three tight sentences, front-loaded with the core action, then the notable default, then the undo behavior. No filler.

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 18-parameter tool with no annotations and no output schema, the description is thin: it does not explain that parameters are type-dependent (only some apply per type), what the default name is, or what the call returns. Adequate but with clear gaps.

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 72% and the schema itself already documents per-type meanings for size, shape, fill, font, and color. The description adds only the text center-justification default and implies type-dependent parameter behavior, which is marginal value over the schema.

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 (create) and the exact set of resources it can make (text, shape, solid, adjustment, null layer), which cleanly distinguishes it from siblings like ae_create_comp and ae_set_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?

Names one alternative with its selecting condition: 'use ae_center_layers to center any layer visually.' That is genuine routing guidance, but it only covers the centering case; there is no broader when-to-use framing or prerequisites (e.g. that a comp must be open).

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