unity_gameobject_set_transform

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

No annotations are provided, and the description does not disclose behavioral aspects such as whether the operation overwrites existing transforms, if it is undoable, or if it has any side effects. The schema hints at local vs world but the description omits this detail.

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 sentence, which is concise, but it lacks crucial information for correct usage. It is front-loaded but under-informative.

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 the tool's complexity (7 params, nested objects, no output schema, no annotations), the description is insufficient. It fails to explain how to identify the GameObject, the difference between local and world space, and safety considerations for a mutation operation.

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 57%, and the description adds no meaning beyond listing 'position, rotation, scale'. It does not explain that these are optional, their default values, or that the port parameter is critical for multi-instance routing.

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 transform (position, rotation, scale) of a GameObject, using specific verbs and resource. It effectively distinguishes from sibling tools like unity_gameobject_info or unity_gameobject_create.

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 on when to use this tool vs alternatives, no mention of prerequisites (e.g., needing a GameObject selected or identified via path/instanceId), and no discussion of which parameters are required or optional.

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