ae_collect_files

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

With no annotations provided, the description must carry the behavioral burden, and it only says 'Collect' without explaining whether files are copied or moved, whether the original project is modified, whether dependencies are included, or whether files are overwritten. The AE command analogy hints at behavior but leaves critical side effects unstated.

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 one sentence, front-loaded with the action and target, and the parenthetical analogy adds useful context without waste. 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 an operation that writes multiple files to disk, the definition omits key context: success/failure behavior, whether the output folder is created or must already exist, whether original assets remain in place, and whether the project must be saved first. The absence of an output schema makes these gaps more significant.

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 the one parameter, output_folder, is defined as 'Absolute path to the destination folder.' The description adds no extra semantics beyond this, but because the schema already covers the parameter, the 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 clearly states a specific operation (collect assets) and a specific target (a single folder), and the AE 'Collect Files' analogy anchors meaning for users familiar with After Effects. It is distinct from siblings like ae_save_project or ae_export_frames, though it does not explicitly name or contrast alternatives.

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 gives no guidance about when to use this tool versus alternatives, no prerequisites, and no exclusions. It implies usage only through the stated purpose, but does not tell an agent whether to pick this over ae_save_project, ae_export_frames, or a folder-creation workflow.

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