ue_landscape_set_material

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral side effect: 'cambiarlo cambia la lista' (changing it changes the list of paintable layers), which adds useful context. However, it omits other relevant behavioral details such as prerequisites (e.g., landscape selection), reversibility, or whether painted layers are affected, leaving gaps for a mutation tool.

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 short sentences in Italian, immediately stating the action and then adding the crucial context about target layers. Every word earns its place; there is no waste or repetition, and it is appropriately 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?

For a simple set-material operation, the description covers the essential side effect and provides some context. However, it lacks explanation of the label parameter, does not mention any prerequisites or conditions, and with no output schema it leaves the return behavior unspecified. It is adequate but has clear gaps.

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 schema has no descriptions for the two parameters (material_path and label), and the description only indirectly references material_path through the concept of 'material'. The label parameter is completely unexplained, and the description does not compensate for the 0% schema coverage. This leaves the agent guessing about label's purpose and format.

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 uses a specific verb ('Assegna' = assigns) and resource ('materiale al landscape'), clearly stating the tool's function. It further distinguishes itself from sibling landscape tools by explaining the material's role in defining paintable target layers, which is unique to this operation.

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 clear context for when to use this tool: when you need to assign a material that determines the paintable target layers. It doesn't explicitly name alternatives or exclusions, but it implies the use case by explaining the consequence of changing the material. This meets the 'clear context, no exclusions' level.

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