ue_landscape_import_heightmap

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

With no annotations, the description carries full burden and does so thoroughly: it warns that the tool overwrites existing terrain and is not undoable beyond editor undo, explains the render-target mechanism, and notes format-specific behavior like the R/G channel reading for 16-bit heightmaps.

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-structured: a one-sentence purpose, a short technical explanation, and a clear Args list. Every sentence adds value and there is no padding.

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?

Given no annotations and no output schema, the description still provides everything an agent needs to select and invoke the tool: purpose, mechanism, prerequisites, parameter semantics, and destructive behavior. Minor edge cases like label omission are not covered, but the core selection and invocation context is complete.

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 Args section explains every parameter despite 0% schema coverage: image_path local file types and resolution prerequisite, label disambiguation, rt_format options with bit-depth implications, and from_rg_channel behavior for float formats. This fully compensates for the 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 opens with a specific action: 'Sovrascrive l'heightmap di un landscape con un'immagine dal disco' (overwrites a landscape's heightmap with an image from disk). This clearly distinguishes it from sibling tools such as ue_landscape_export_heightmap and ue_landscape_import_weightmap.

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?

It provides clear usage context: the image must be at the landscape's resolution because the render target won't rescale, and it explains the render-target approach is the only way Unreal accepts a heightmap via script. It doesn't explicitly name alternatives or when not to use this tool, so it isn't a 5.

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