set_actor_transform

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'set', which implies mutation, but does not mention coordinate space, units, side effects such as physics interference, whether the transform is applied in world space, or failure modes. The example is too minimal to clarify behavior.

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 short and front-loaded with the core purpose. The KB reference and example are useful and do not add redundancy. It could be slightly more informative, but it is efficient and well-organized.

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 mutation tool with four parameters and no annotations, this description lacks key contextual details. It does not explain the expected array formats, the meaning of omitting parameters, or the operational context in the Unreal editor. The KB reference partially compensates, but the description itself is not sufficient for correct invocation.

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 compensate. It names location, rotation, and scale, which roughly maps to the three array parameters, but it does not explain array ordering, units, valid ranges, or what null defaults mean. The example only shows the required name parameter, omitting the transform parameters entirely.

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 a clear verb and resource: 'Set the transform (location, rotation, scale) of an actor.' It identifies exactly what the tool does and which fields are affected. It does not explicitly distinguish from siblings such as set_actor_property, but the transform focus is unambiguous.

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 given about when to use this tool versus alternatives like set_actor_property or add_set_actor_location_node. The KB reference points to a world-building overview, but it does not explain the intended workflow, prerequisites, or exclusions.

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