Move an After Effects project item into a specific folder by providing the item name and destination folder name.
Move a project item into a folder
| Name | Required | Description | Default |
|---|---|---|---|
| item_name | Yes | Name of the item to move | |
| folder_name | Yes | Destination folder name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the action without mentioning whether the folder must already exist, whether references are updated, what happens on failure, or any side effects of the move.
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?
A single clear sentence with zero filler. It is front-loaded and directly communicates the operation without unnecessary words.
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?
The tool is simple with two well-defined string parameters, and the description is understandable. However, there is no annotation or output schema, and the description omits preconditions such as requiring an existing destination folder or an open After Effects project, leaving minor gaps in operational completeness.
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% and both parameters are already well described in the schema. The description adds minimal semantic value beyond 'move' and 'destination folder', but the schema already provides the necessary parameter meaning.
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 specific verb ('Move') and resource ('project item') with a clear destination ('into a folder'). It is distinct from sibling tools like ae_create_folder and ae_delete_project_item, so an agent can understand exactly what this tool does.
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 no guidance about when to use this tool instead of alternatives such as ae_create_folder, ae_list_project_items, or ae_delete_project_item. There are no explicit conditions, exclusions, or references to related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.