Import Folder

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not say whether subfolders are recursed, whether bins are created, or what happens if the folder was already imported.

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, front-loaded sentence with no padding or repetition. It is efficient, though it is arguably too terse for a mutation tool of this scope.

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?

An output schema exists, so return values need not be explained, and one fully documented parameter is simple. Still, for a folder-level ingest operation the description omits recursion behavior, duplicate handling, and target bin destination—gaps an agent would want before calling it.

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?

Only one parameter exists and the schema documents it at 100% coverage ('Path to the folder to import'). The description provides no additional syntax, path-format, or relative-vs-absolute guidance, so it lands at the baseline for fully covered schemas.

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?

States a clear verb and resource: importing a whole folder of media into the project. The scope word 'entire' distinguishes it from a single-file import, but the description never names or contrasts with siblings such as import_media, import_image_sequence, or import_sequences.

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 indication of when to choose this over import_media or import_image_sequence, and no preconditions (project must be open, media must be online, behavior on overlapping items) are given. The agent must infer routing from the tool name alone.

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