ue_list_assets

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

The description discloses the main behavior: listing assets recursively with optional class filtering. No annotations are provided, but the description does not reveal potential issues like what happens if the path is invalid or if there are many assets. However, the output schema exists to clarify return format.

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 concise (one sentence plus bullet-like args). It is front-loaded with the main purpose, 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?

The description covers the main functionality and parameters. With an output schema present, it does not need to detail return values. However, it lacks mention of error handling or edge cases, which would improve completeness.

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 description adds meaning beyond the schema by explaining each parameter: path as an Unreal folder, recursive includes subfolders, and class_filter is a partial class name filter. This is crucial since the schema only provides titles and defaults.

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 'Lists assets under a Content Browser path' using a specific verb and resource. It distinguishes itself from sibling tools like 'ue_list_actors' which list actors in a level.

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 on when to use this tool versus alternatives. While the parameter descriptions help understand usage, there is no mention of when to prefer this over similar tools like 'ue_import_assets' or 'ue_list_actors'.

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