batch_import_folder

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

With no annotations provided, the description carries the full burden and does a solid job: it explains the local scan phase, the single exec_python call to UE5, per-file AssetImportTask usage, dry-run behavior, and per-file result reporting. It does not disclose potential overwrite side effects or failure modes, but the core behavior is transparent.

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 well-organized with a summary, Args, Returns, KB reference, and Example. It is longer than minimal, but the length is justified by 8 parameters and a complex batch workflow. Every section 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?

The description is complete enough to call the tool correctly: it provides return JSON, dry-run behavior, and a KB reference. Minor gaps remain, such as not enumerating which file types count as "recognised assets" and not stating whether UE5 must be running for the import phase, but these are not blocking.

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 0%, but the Args section compensates fully by explaining all 8 parameters, including folder_path as an absolute path on the MCP server machine, defaults for all booleans, and the ue5_base_path Content Browser semantics. This adds significant meaning beyond the bare schema.

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 names a specific verb and resource: "Batch-import all recognised assets from a local folder into UE5." This clearly differentiates it from sibling single-asset import tools by emphasizing batch scanning of a folder.

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 implies when to use it: when you have a local folder of assets to import in batch. However, it never names alternatives or states when not to use it, such as importing a single asset or using a character-specific import workflow, leaving routing to the agent's inference.

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