set_transform

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

With no annotations, the description carries full behavioral burden. It discloses the most non-obvious behavior—unspecified transform components are left unchanged—and scopes the mutation to world space. It does not mention failure behavior, but the output schema covers return values and the partial-update caveat is the important part.

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?

One focused sentence with the key behavioral caveat embedded in a parenthetical. Every word earns its place and the core operation is front-loaded.

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?

Despite the output schema, the definition is not complete enough for correct invocation: an agent cannot know the array conventions for the three numeric parameters or whether a transform component must already exist. The short description is clear but under-specified for a setter with no annotations and no schema descriptions.

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 0%, and the description does not compensate. It never explains the expected array shapes/order or rotation convention for position, rotation, and scale, and does not say what 'provided' means for component creation. The partial-update phrase is useful but leaves almost all parameter-level details to inference.

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 states a specific operation ('Set the world transform of an entity') and adds a key distinguishing constraint ('only provided components are changed'). This clearly differentiates it from read-only get_transform and general set_component_property.

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 intended use is inferable: use it when you need to modify an entity's world transform. However, the description gives no explicit guidance about when to prefer it over set_component_property, no prerequisites, and no exclusions.

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