set_prim_transform

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=false), so the bar is lower, but the description adds nothing beyond them. It does not say whether omitted components are left unchanged, whether the prim must already exist, or whether the prim must be xformable.

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?

Single short sentence, front-loaded and free of padding, but its brevity comes at the cost of under-specification rather than efficiency. It earns its place but does too little work.

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 four parameters, an output schema, and no parameter-level help in the description, critical semantics are missing: partial-update behavior, existence requirements, and failure modes. The output schema covers return values, but the mutation contract is undocumented.

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 100%, with the schema itself documenting units (metres), Euler degrees vs quaternion, and uniform vs per-axis scale. The description contributes no additional parameter meaning, so baseline 3 applies.

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?

States a specific verb (set) and resource (position/rotation/scale of a prim), which clearly distinguishes it from create_prim, delete_prim, and clone_prim. It stops short of noting that components are optional, but the core action is 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?

No guidance on when to use this versus siblings such as look_at_prim (which also sets orientation) or create_prim, and no exclusions or prerequisites stated. An agent must infer usage entirely from the name.

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