set_actor_property

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

With no annotations, the description carries the full burden. It offers extensive behavioral details: the types supported, dotted-path syntax for nested properties, the polymorphic nature of the value parameter, and a version limitation (FInstancedStruct deferred). This far exceeds typical descriptions.

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 relative to the amount of information conveyed. It front-loads the main action and then lists supported types and limitations. While slightly long, every sentence adds value.

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?

Given no output schema, the description adequately explains input semantics and supported types. It mentions common UE structs but doesn't enumerate them all, and the sibling list provides context (e.g., bulk_set_actor_property). This is sufficient for a developer familiar with Unreal Engine.

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?

The input schema covers all three parameters with descriptions (100% coverage). The description adds significant meaning beyond the schema: it explains dotted-path syntax for the property parameter, the polymorphic coercion logic for value, and the rationale for the value schema design. This provides crucial context for correct invocation.

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 explicitly states the tool mutates a UPROPERTY on an actor, lists supported types (primitives, structs, enums, TSoftObjectPtr, etc.), and mentions dotted-path syntax for nested properties. This clearly distinguishes it from siblings like bulk_set_actor_property or 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 does not provide explicit guidance on when to use this tool versus alternatives like bulk_set_actor_property. It notes a limitation (FInstancedStruct deferred to v0.4.x) but does not state use cases or exclusions. Usage is implied through the tool's purpose.

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