object.transform_set

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

With no annotations, the description carries full burden for behavioral transparency. It only states the tool's purpose without disclosing whether it overwrites all fields, requires an existing object, or has side effects. This is insufficient for an AI agent to understand the tool's behavior.

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 extremely concise—one sentence. It is front-loaded and has no wasted words, but it is so minimal that it sacrifices informativeness. It could be expanded without becoming verbose.

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 the tool's complexity (8 parameters, no output schema, no annotations), the description is woefully incomplete. It does not explain the effect of combining parameters, the behavior of delta vs absolute transforms, or how errors are handled. An agent cannot reliably invoke this tool correctly based solely on the description.

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 adds no parameter explanations beyond what the titles provide. For 8 parameters, it does not clarify differences between location/delta_location, rotation/delta_rotation, or the effect of rotation_mode. The agent must infer from parameter names and types alone.

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 'Set an object's transform fields' uses a specific verb and resource, clearly indicating the action and target. It distinguishes from siblings like object.transform_get and object.transform_apply, though it could be more explicit about which fields (e.g., location, rotation, scale).

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives like scene.set_transform or rig.set_bone_transform, nor does it mention prerequisites or typical use cases.

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