set_object_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 discloses a key behavior: 'Only provided channels are modified,' which prevents accidental overwriting of unspecified channels. It also specifies that rotation is in radians and that space can be WORLD or LOCAL. However, it does not mention potential side effects (e.g., effect on children, absolute vs relative positioning) or error conditions, leaving some ambiguity for an agent. Still, it covers the most critical behavioral detail.

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 and well-structured. It opens with the core purpose in one sentence, then provides a compact args list that is immediately readable. There is no fluff, and every sentence earns its place. The front-loaded summary and organized parameter explanations make it easy for an agent to parse quickly.

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?

For a mutation tool with no output schema, this description is fairly complete. It explains the input parameters and the key behavior of selective modification. It does not mention return values or error handling, but those are often implicit for such operations. Given the complexity of the tool (5 parameters, space selection) and the lack of annotations, it provides enough context for an agent to call it correctly. The only missing piece is clarification on absolute vs. relative transforms or effects on child objects, but these are not critical for basic 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?

The description includes an 'Args' section that explains each parameter: name (object name), location ([x,y,z] position), rotation ([x,y,z] Euler rotation in radians), scale ([x,y,z] scale factors), and space (WORLD or LOCAL). This adds meaning beyond the raw schema, which only provides types and defaults. It clarifies the format and units, which is essential given the schema has no descriptions (0% coverage). It covers all five parameters adequately.

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 tool's function: 'Set world/local transform of an object' with a specific resource (an object) and the ability to modify multiple transform channels at once. It also notes 'Only provided channels are modified,' which distinguishes it from single-purpose siblings like move_object, rotate_object, and scale_object. This is precise and unambiguous.

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 implies when to use it (when you need to set one or more transform properties in a single call, possibly in world or local space) but does not explicitly mention alternatives or exclusions. For example, it doesn't say 'for moving only, use move_object.' However, the existence of sibling tools like move_object and rotate_object makes the context clear enough, but the lack of explicit routing prevents a higher score.

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