ae_delete_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 of disclosing behavior. It only restates the deletion operation and does not mention irreversibility, effects on dependent layers, expressions, or render queue references, or failure behavior for missing comps/layers.

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, efficient sentence with zero filler or repetition of schema fields. It front-loads the core action and is appropriately sized for such a simple tool.

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?

Basic invocation is possible because both required parameters are fully documented and the operation is simple. However, for a destructive action with no annotations and no output schema, the description omits key context such as whether deletion is undoable, whether related layer data is removed, and what happens if the comp or layer is invalid.

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?

The input schema already provides 100% coverage with descriptions for both comp_name and layer_name. The tool description adds no additional semantic detail about parameter formats, relationships, or preconditions, so the baseline score of 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 ('Delete'), the object ('a layer'), and the containing context ('from a composition'). This unambiguously distinguishes it from related siblings such as ae_delete_composition and ae_delete_project_item.

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?

There is no guidance about when to use this tool versus alternatives, no exclusions, and no mention of prerequisites like an open composition. The only usage signal is the imperative description itself, which provides minimal context for selecting between this and similar deletion tools.

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