set_transform

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

No annotations are present and the description omits key behaviors such as coordinate space (local vs. global), whether null values leave components unchanged, and how relative mode combines with existing transforms (scale is multiplicative, but position/rotation not detailed).

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 compact and directly conveys the core purpose of the tool. However, it is terse enough that important nuances (like null handling) are omitted, though overall it remains efficient.

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?

The tool has moderate complexity with 5 parameters and relative-mode logic, but the description provides insufficient context about object selection, coordinate frames, and default behaviors. More details are needed for correct usage.

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%; the description does not explain parameter details like array length, null semantics, or that rotation is in radians Euler (beyond the brief parenthetical). No parameter-specific information is added.

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?

Description explicitly states it sets position, rotation, and scale, and clarifies the behavior of relative mode. This uniquely identifies the tool among many transform-related siblings.

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 compared to alternatives like batch_transform or randomize_transform. It is implied that it operates on a single selected object but this is never stated.

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