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 of behavioral disclosure. It states the operation is a setter (implying mutation) but does not disclose possible failure modes, whether the property must already exist, how type coercion works, or whether the change is persistent or session-only. This is a significant gap for a mutation tool.

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 a single, focused sentence that is immediately scannable and contains no filler or redundant content. It efficiently states the core functionality.

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?

The tool is a simple generic setter, but the description omits observable behavior such as expected return value, error handling on invalid property names, or interaction with the Remote Control API's restrictions. Given the absence of annotations and output schema, a bit more context would make this a more complete description.

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 schema provides descriptions for all three parameters, including a clear example for actor_path and a minimal 'Value to set' for property_value. The description adds no additional parameter-level meaning, so the schema carries the burden. Baseline 3 is appropriate because schema coverage is 100%, but property_value's semantics are thin.

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 the action ('Set') and resource ('property on an actor'), and specifies the API context ('Remote Control API'). It is sufficiently distinct from siblings like set_actor_transform and set_actor_tags because it targets an arbitrary named property, though it could more explicitly convey "arbitrary" or "generic."

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 set_actor_transform, set_actor_tags, or the Niagara-specific property setters. The description does not mention any prerequisites (e.g., actor must exist, property must be accessible) or when a more specialized setter would be preferable.

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