import_folder

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

The description does not disclose important behavioral details like whether subfolders are included, if media is copied or linked, or any file type restrictions. Annotations only indicate non-readonly and non-destructive, but the import could have side effects not explained.

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 sentence of 8 words, highly concise. However, it sacrifices information for brevity, but still meets the minimal bar for clarity.

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?

Given no output schema and low complexity, the description leaves out key contextual information such as expected folder structure, error conditions, or any project-side effects. It is not fully complete for an agent to use reliably.

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 coverage is 100% with the single parameter having a description. The tool description adds no extra meaning beyond the schema's 'Path to the folder to import'. Baseline 3 applies.

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 (import), resource (entire folder of media), and destination (into the project). It distinguishes from siblings like import_media which imports individual files.

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 provided on when to use this tool vs alternatives such as import_media, import_image_sequence, or import_ae_comps. The user must infer from the name alone.

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