set_material_on_actor

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

No annotations are provided, so the description carries the full behavioral burden. It makes clear this mutates an actor's material and connects it to the UE 'Set Material' node, but it does not disclose persistence, side effects, failure behavior, or prerequisites such as the material asset needing to exist.

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-line purpose, a short context note, a compact Args block, a KB pointer, and an example. Each section adds useful information without unnecessary filler.

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 three-parameter mutation with an output schema and an example, the inputs are fully specified and the operation is scoped to static mesh actors. It omits side-effect and failure-mode details, but the narrow scope and KB reference make it sufficiently complete for an agent to invoke.

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 description coverage is 0%, but the Args block fully compensates by explaining all three parameters with concrete examples, including the actor name format, asset path format, and the meaning of element_index with its default.

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 opening sentence, 'Set a Material on a static mesh actor in the level,' names a specific verb, resource, and target type. It clearly distinguishes this operation from the many blueprint-node, import, and property tools in the sibling list.

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 gives a concrete scenario (the Chapter 5 CylinderTarget changing Material when hit) and a book reference, which implies when to use it. However, it does not explicitly state when not to use it or compare it with alternatives like set_static_mesh_properties or add_set_material_node.

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