Set Transform

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

Annotations declare non-readOnly, idempotent, non-destructive, which the description does not contradict. The description adds genuinely useful behavior beyond the annotations: the coordinate space per field (position world, rotation world euler degrees, scale local) and the partial-update contract, both critical to getting correct results.

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?

Three short, front-loaded sentences: the operation, the partial-update rule, then a concrete example. Every sentence earns its place with no filler.

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 no output schema and a completely empty input schema, the description supplies the essential calling information (fields, spaces, partial semantics, example). It omits error behavior and what happens if the named object is not found, which are minor but real gaps.

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 input schema is empty, so the description carries the full burden and does supply the meaningful field names (path, position, rotation, scale), their coordinate spaces, and a concrete call example. It stops short of a formal field list, defaults, or required-vs-optional markers beyond the example's implication that path is needed.

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?

States a specific verb (set) and resource (transform) and enumerates the three affected properties with their coordinate spaces, so the agent knows exactly what changes. It does not, however, distinguish itself from close siblings such as unity_set_component_property or unity_create_gameobject, which also mutate scene objects.

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?

"Provide only fields to change" implies partial-update semantics, which is useful usage guidance. But there is no statement of when to prefer this over unity_set_component_property or unity_execute_code, and no prerequisites (e.g., the target object must already exist).

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