Set Object Transform

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

No annotations provided; description carries full burden. It discloses key behaviors: partial patching keeps unspecified values, matrix replaces entire transform, space selection, and mutual exclusivity. Minor omission of error handling or side effects, but adequate for a write tool.

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?

Four sentences, front-loaded with purpose, no fluff. Each sentence adds essential information: mode options, patching details, matrix replacement, space defaults with internal names.

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?

Covers all key aspects: input modes, parameter relationships, space choices. No output schema exists, but return values are not critical for a write tool. Minor gaps in error behavior or prerequisites, but complete for typical use.

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 has 100% coverage with descriptions, but description adds significant value: explains patching semantics, matrix row structure, and rotation units (HPB radians). This enhances understanding beyond the schema 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 clearly states it writes an object's transform in local or global space, with options to patch individual components or replace with a full matrix. It distinctly separates from sibling tools like set_params (generic) or move_entity (position-only) by focusing on transform operations.

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?

Provides explicit guidance on when to use patching vs. matrix replacement, explains mutual exclusivity, and clarifies space defaults and global mode. However, it lacks explicit 'when not to use' or alternatives, though context makes it sufficient.

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