unity_gameobject_set_transform

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

No annotations are present, so the description bears full responsibility. It only says 'Set the transform' without disclosing consequences (e.g., permanent modification, coordinate system defaults, or potential errors). This lack of transparency limits informed usage.

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 with no wasted words. It is front-loaded with the core action, but the extreme brevity sacrifices informative value.

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 no output schema and a brief description, the tool's behavior is under-explained. Users need context about coordinate systems, instance handling, and error states, which are not covered.

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 description mentions 'position, rotation, scale', matching three nested object parameters, but adds no detail beyond the parameter names. Schema coverage is 57% (some parameters like path have descriptions), so the description provides marginal additional meaning.

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 verb 'Set' and resource 'transform (position, rotation, scale) of a GameObject', making the purpose clear. However, it does not distinguish from related sibling tools like unity_gameobject_set_active or unity_gameobject_create, though the operation is distinct.

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 provided on when to use this tool versus alternatives. The description omits prerequisites such as needing an active Unity instance or a valid GameObject path, which are hinted at by the schema but not explicitly stated.

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