ue_landscape_import_weightmap

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

With no annotations, the description must cover behavior. It discloses the color mapping (white=max, black=absent) and prerequisite that the layer must pre-exist. However, it does not mention potential overwriting, image format/size requirements, or result reporting, leaving notable behavioral gaps.

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 two sentences, front-loaded with the main action, and ends with the key prerequisite. Every word earns its place with no fluff or repetition.

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 the tool's moderate complexity, no annotations, no output schema, and 0% schema description coverage, the description provides essential context (color mapping, prerequisite) but omits critical operational details like supported image formats, overlay behavior, and any return values. It is minimally viable but not comprehensive.

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 0%, so the description must compensate. It implicitly relates layer_name (target layer) and image_path (immagine), but does not explain the rt_format or label parameters at all. The coverage is incomplete and not explicit enough for an agent to confidently fill all parameters.

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 it paints a landscape layer from a grayscale image, using an explicit verb (Dipinge) and resource (layer del landscape). It distinguishes from sibling tools like ue_landscape_import_heightmap by focusing on weightmap layers rather than heightmaps.

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 context: the layer must already exist and lists where to find available layers via ue_landscape_info. It does not explicitly mention when to avoid this tool or directly compare with alternatives like the heightmap importer, but the precondition and reference to a sibling tool give solid guidance.

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