Unity Set 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 states that the tool sets transform properties, implying mutation, but does not disclose any behavioral traits such as side effects on child objects, coordinate system nuances (e.g., setting position affects world space), or potential conflicts with other components. The description is too minimal to be transparent.

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, front-loaded sentence that efficiently conveys the essence. However, given the complexity of the tool (5 parameters, nested objects), it could slightly expand on key aspects without becoming verbose. Still, it is appropriately concise and avoids unnecessary words.

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?

With 5 parameters (1 required), no output schema, and no annotations, the description is incomplete. It fails to clarify what happens when optional parameters (position, rotation, scale) are omitted, how the tool interprets null or partial inputs, or what the return value (if any) indicates. The schema properties provide some context, but the description does not integrate or explain the tool's overall behavior sufficiently.

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 has 100% description coverage, with each parameter already described (e.g., 'World position', 'Euler rotation in degrees', 'Local scale'). The tool description merely repeats these names without adding new context, such as behavior when a parameter is omitted or typical value ranges. Hence, it provides no additional meaning beyond the schema, earning a baseline score of 3.

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 uses a specific verb 'Set' and clearly identifies the resource ('a GameObject's Transform'). It lists the three aspects (position, rotation, scale) that can be modified, making the purpose immediate and distinct from sibling tools like unity_get_gameobject or unity_set_gravity.

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 over alternatives. There is no mention of prerequisites, preferred scenarios, or exclusions. For a tool that modifies transform, users might need to know when to use this versus unity_set_component_property or other transform-related tools, but none is offered.

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