set_actor_transform

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

With no annotations provided, the description carries the full burden. It implies mutation but does not disclose whether updates are partial or absolute, what coordinate space is used, units for rotation, error behavior, or return value. The 'and/or' hint is the only behavioral nuance.

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?

A single sentence with ten words, front-loaded and without filler. Every word earns its place.

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 three nested object parameters, no annotations, no output schema, and minimal description, the tool is under-specified. The description does not clarify partial updates, required actor checks, or rotation format, making it insufficient for safe autonomous use.

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 only 25% (only 'name' has a description). The description lists the three transform properties but adds no semantic meaning beyond their names—e.g., units, coordinate system, or that each property is independently optional.

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 the location, rotation, and/or scale of an actor, specifying both the verb and the resource. It distinguishes from generic sibling tools like set_actor_property by naming the specific transform components.

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 such as set_actor_property or spawn_actor. There is no mention of prerequisites, use cases, or exclusions.

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