import_texture

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

No annotations are provided, so the description carries the full burden. It states 'canonical UE asset import pipeline' but does not disclose side effects such as file overwrite behavior (handled by replace_existing, not described), disk writing, or error handling. For a mutation tool without annotations, this is insufficient.

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, well-structured sentence that conveys the core functionality without extraneous words. Every part is meaningful and front-loaded.

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 adequate for basic understanding, but with 6 parameters and no output schema or annotations, it lacks details on parameter interactions (e.g., automated, save), success/failure return values, and advanced import scenarios. It covers the essentials but misses some behavioral context.

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 coverage is 100%, so the baseline is 3. The description adds value by listing supported formats (not in schema), but does not elaborate on individual parameters like 'automated' or 'save' defaults beyond what the schema already provides.

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 specifies the action ('Import an image file'), the input formats (PNG/JPG/EXR/TGA/BMP/HDR), the asset type (UTexture2D), and the use of 'canonical UE asset import pipeline', clearly distinguishing it from siblings like 'configure_texture' or 'convert_hdri_to_cubemap'.

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 basic usage (when to import a texture), but lacks explicit guidance on when not to use this tool versus alternatives like 'configure_texture' for post-import settings or 'marketplace_import' for marketplace assets. No prerequisites or exclusions are mentioned.

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