Delete a named item from the After Effects project panel to clean up unused assets.
Delete an item from the After Effects project panel
| Name | Required | Description | Default |
|---|---|---|---|
| item_name | Yes | Name of the item to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral disclosure burden. It only says 'Delete an item' without noting irreversibility, effects on compositions that reference the item, or any failure conditions. For a destructive operation, this is a significant transparency gap.
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, clear sentence with no redundant words. The core action is front-loaded, and it is appropriately sized for the tool's simplicity.
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 one-parameter, no-output-schema tool, the description is minimal but adequate. However, it does not clarify what counts as an 'item' (e.g., folders, compositions), how the tool behaves if the item is in use, or name-matching rules. These gaps are notable for a destructive operation but not crippling given the simple interface.
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 100%, with the only parameter item_name described as 'Name of the item to delete.' The tool description adds the 'project panel' context but does not otherwise enrich parameter semantics beyond the schema. Baseline 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 states a clear verb and resource: 'Delete an item from the After Effects project panel.' It differentiates from sibling tools like ae_delete_layer and ae_delete_composition by specifying the project panel as the location. However, it does not clarify whether 'item' includes compositions, folders, or footage, leaving slight ambiguity alongside ae_delete_composition.
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?
No guidance is given on when to use this tool versus alternatives such as ae_delete_composition, ae_delete_layer, or ae_remove_render_queue_item. The description does not mention exclusions or conditions, so an agent must infer usage solely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.