ae_add_adjustment_layer

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

With no annotations provided, the description carries full burden. It discloses that the layer is added full-frame and at the top, but does not mention side effects, destructiveness, permissions, or undo capabilities. More context needed for a null-annotation 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?

Single sentence, front-loaded with action and resource, no extraneous information. Every part earns its place.

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 simple 2-param tool with no output schema, the description is adequate but missing details about return value and whether the layer is immediately visible or if further setup is needed.

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 0%, so the description should compensate. It only suggests the 'name' parameter has a default value 'Adjustment' and implies 'comp' exists, but does not explain what either parameter is for or provide usage details.

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 verb 'Add' and resource 'adjustment layer' with specific context 'full-frame at the top of the stack'. It distinguishes from sibling tools like ae_add_layer_to_comp which adds generic layers, and ae_add_effect which adds effects to existing 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?

The description provides clear usage context: use this tool to apply global effects via ae_add_effect or ae_add_glow. It implicitly indicates when to use it but does not explicitly state when not to use it or mention alternatives aside from the referenced effect tools.

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