set_static_mesh_material_slot

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds the return payload including a 'saved' flag, hinting that the change is persisted, but it does not explain that an assignment overwrites the previous material or whether the change is undoable, which is the key destructive behavior an agent needs.

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?

Two tight sentences with zero filler, and the core action is front-loaded before the return shape. Nothing needs trimming.

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?

With no output schema, the description usefully enumerates the return fields, and the annotations cover the read/write safety profile. The remaining gap is overwrite semantics for the existing slot, which would matter for a destructive operation.

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 100%, so all three parameters (static_mesh_path, material_path, material_index) are documented in the schema itself. The description only reframes the operation around slots and adds no syntax, format, or indexing detail beyond what the schema provides; baseline 3.

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?

States a specific verb and resource ('Assign a material to an existing material slot of a static mesh'), which is unambiguous about what the tool does. The resource name distinguishes it from set_skeletal_mesh_material_slot, but the description never explicitly differentiates between the two, so it falls short of a 5.

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 phrase 'existing material slot' implies the slot must already exist, which is a useful precondition, but there is no explicit when-to-use, when-not-to-use, or alternative tool guidance. Usage is implied rather than stated.

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