preset_library_list

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

With no annotations, the description carries full behavioral burden. It discloses the default library path and that paths are intended for import, but lacks details on whether filters (subfolder, extensions) are applied, recursion, or absolute paths. It provides basic transparency but is incomplete.

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?

Two sentences, front-loaded with the action, no wasted words. Efficiently communicates the core purpose and a critical usage hint about feeding paths to another tool.

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 tool is simple with two optional params and no output schema. The description covers the basic use but is incomplete: it does not describe the return format beyond 'paths', and parameter semantics are missing. Partially compensates by linking to ue_import_assets.

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?

Input schema has 0% description coverage, and the description does not explain the 'subfolder' or 'extensions' parameters at all. Despite two optional parameters, the description omits their meaning or how they affect the listing, leaving the agent without guidance.

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 lists files already downloaded in the local library ('Elenca i file già scaricati nella libreria locale'), a specific verb+resource. It also mentions the default path and that returned paths can be passed to a sibling tool (ue_import_assets), distinguishing its purpose.

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 provides context for when to use it: to list local library files before importing via ue_import_assets. It implicitly guides usage but does not explicitly mention when not to use or compare to sibling list tools like ue_list_assets.

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