ue_assign_material

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

No annotations are provided, so the description bears the full burden. It does not disclose behavioral traits such as required permissions, side effects (e.g., asset modification), or conditions (e.g., actor must have a mesh). Only the basic action is stated.

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 short, combining an Italian title line with English parameter documentation. It is structured but uses two languages, which could be streamlined. Every line adds value without unnecessary verbosity.

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 explains the action and parameters but omits return behavior, error conditions, and prerequisites. Given no output schema or annotations, a bit more context (e.g., 'returns nothing on success') would improve completeness.

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 input schema has 0% description coverage, but the tool's description provides clear explanations for all 4 parameters: label (actor label), material_path (path), slot (index with default 0), component (default first MeshComponent). This adds significant meaning beyond the schema's type/title-only fields.

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 'Assegna un materiale a un attore piazzato' (assign a material to a placed actor), specifying the verb and resource. It distinguishes from sibling tools like ue_set_actor_property or ue_create_material by being material-specific.

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 usage when a material needs to be assigned to an actor, but provides no explicit guidance on when not to use it or alternatives. No differentiation from other actor manipulation tools.

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