import_folder

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states that media files are imported, but it does not disclose whether a bin is created, what happens when the folder is empty, whether existing items are duplicated, or what side effects occur in the project.

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, focused sentence that immediately communicates the core action and the target context. There is no filler, repetition, or unnecessary detail.

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 mutating import tool with no annotations and no output schema, the description is thin. It omits important invocation context such as default behavior when binName is omitted, whether recursive defaults to false, error handling, and what counts as a supported media file. An agent has to infer too much before calling this tool confidently.

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%, so the parameter descriptions already define folderPath, binName, and recursive. The tool description adds no new parameter semantics beyond the broad 'imports all media files from a folder,' which is expected given the schema already documents the parameters clearly.

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 operation: importing all media files from a folder into the current Premiere Pro project. It uses a specific verb and resource, and it is distinct from siblings like import_media or import_sequences by emphasizing folder-level bulk import.

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 on when to use this tool versus alternatives such as import_media, import_sequences, or import_image_sequence. It does not mention when folder-level import is appropriate or when one of the more specific import tools should be chosen instead.

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