ue_set_actor_property

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

The description discloses behavior such as automatic loading of asset paths and JSON formatting for vectors and colors. It explains scope (actor or component) and parameter usage. However, it does not mention undo behavior or error handling, which is acceptable for a property setter.

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 concise (~100 words) and well-structured, with a clear main sentence followed by supporting details and an Args list. Every sentence is informative and necessary.

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 property-setting tool with no output schema, the description covers the core functionality, input format, and scope. It lacks error behavior or edge-case handling, but is largely complete for typical use.

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?

With 0% schema description coverage, the description compensates fully by explaining each parameter (label, component, properties) with examples, including the component's default behavior and the structure of property values.

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 it sets properties on an actor or its component, with specific examples like mesh, light intensity, trigger radius. It distinguishes itself from sibling tools like ue_set_class_defaults and ue_set_actor_transform.

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 explicitly notes it covers everything except Class Defaults of a Blueprint, guiding the agent to use this for instance-level properties. It mentions JSON format for values but doesn't provide explicit when-not-to-use or list alternatives.

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