Unreal Set Actor Transform

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects (e.g., overwrites existing transform, triggers physics updates), coordinate system details, or whether partial updates are allowed. The description is too minimal 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, clear sentence with no extraneous words. It is front-loaded and efficient. However, it may be too terse given the complexity of transform operations.

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?

Despite the schema covering all parameters, the description omits crucial context: no mention of return behavior, error conditions, or constraints (e.g., actor must exist in the level). For a tool with nested parameters and no output schema, this is incomplete.

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 coverage is 100% with clear descriptions for each parameter (path, location, rotation, scale, timeout). The description adds no additional semantics beyond what the schema provides, such as units (degrees vs radians) or world/object space. Baseline 3 is appropriate.

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 tool sets location, rotation, and/or scale of an actor in Unreal. It uses specific verbs and resource, and effectively distinguishes from sibling tools like 'unreal_set_actor_property' (general property) and 'unreal_spawn_actor' (creation).

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 provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., actor must exist), or limitations. It lacks context for the agent to decide between similar tools such as 'unreal_set_actor_property' for individual transform components.

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