unreal_apply_material_to_actor

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

With no annotations provided, the description carries the full burden. It clearly labels the operation as mutating, discloses the editor-open refusal behavior, and mentions the save side effect. It does not, however, explain that dryRun defaults to true, which could prevent actual mutation.

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 with no filler. The core action is front-loaded, and the critical behavioral guard is placed in a separate, easily parsed sentence.

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 7-parameter mutation tool with no output schema and no annotations, the description is not fully self-sufficient. It omits dryRun semantics, timeout behavior, and what the tool returns or verifies after saving. The editor-open guard is helpful, but a crucial default behavior is missing.

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%, so the description must compensate. It gives meaning to map, actorLabel, material, slot, and allowWithEditorOpen, but leaves dryRun and timeoutSeconds unexplained. dryRun is especially important because it defaults to true and directly affects whether the mutation happens.

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 and resource chain: assign a material to a slot on a named actor's static mesh component in a single map, then save. This clearly distinguishes it from siblings like unreal_set_actor_properties or unreal_spawn_actors.

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 context by noting the operation targets one map and requires the editor to be closed unless allowWithEditorOpen is set. However, it never explicitly states when to prefer this tool over alternatives such as unreal_set_actor_properties or unreal_create_material_instance, so usage guidance is only implied.

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