ue_make_folder

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

The description adds the behavioral trait of idempotency, which is valuable. However, it does not disclose what happens if the folder already exists, error cases, or success indicators. With no annotations, the description carries the full burden and is only partially 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 very concise, with two sentences and a bullet-like parameter line. It is front-loaded with the main purpose and idempotency, and every sentence adds value.

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 simple tool with one parameter and no output schema, the description is mostly adequate but lacks details on whether parent folders are created automatically or must exist. The example helps, but important context is missing.

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?

The schema has no parameter description (0% coverage), so the description must compensate. It provides an example path '/Game/MyGame/Meshes', which clarifies the expected format and context. The example adds meaningful semantics beyond just the schema type.

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 tool creates a folder in the Content Browser and mentions idempotency, which distinguishes it from sibling tools that deal with assets, actors, or levels. The purpose is specific and unambiguous.

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 explicit guidance is provided on when to use this tool or prerequisites. The description does not explain if the folder's parent path must exist or how it relates to other operations like importing assets.

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