ue_set_actor_property

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

With no annotations, the description partially compensates by noting that lists of 3 or 4 numbers are coerced to Vector or LinearColor. However, it omits other behavioral details like whether the change is undoable, if the actor must be in a selected state, or if the property change persists.

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 extremely concise with two sentences. The first sentence immediately conveys the main action, and the second adds a useful detail. No redundant words.

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 tool that modifies an actor property in Unreal Engine, the description lacks crucial context: prerequisites (actor existence), result (success/failure), side effects (e.g., transient vs. persistent change), and any assumptions about the editor state. Given no output schema, these gaps are significant.

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 explain all parameters. It only provides an example for property_name and hints at value coercion, but does not clarify the meaning of 'label' or the exact format expected for property_name (e.g., full path vs. simple name).

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 states the tool sets an editor property on an actor, with a concrete example ('intensity'). This clearly communicates the action and resource. However, it does not explicitly differentiate from sibling tools like ue_set_actor_transform, which could cause ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use ue_set_actor_transform or other property setters. There are no prerequisites, exclusions, or contextual hints.

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