load_usd

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

No annotations exist, so the description carries full behavioral burden. It does state that the asset is loaded 'into the scene' and names prim_path/transforms, implying a scene mutation. However, it does not disclose whether an existing prim at prim_path is replaced, whether the operation is idempotent, or what happens on invalid URLs/paths – significant gaps for a load operation.

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: one sentence of purpose followed by four terse, informative parameter explanations. Nothing is redundant, and the actionable purpose is front-loaded.

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?

Core invocation details are present: URL source, target prim path, and transforms. Yet the description omits command_id/idempotency_key semantics, gives no usage or alternative guidance, and does not mention preconditions or side effects. The output schema covers return values, but these gaps make the definition only partially complete.

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 Args block adds meaningful semantics beyond schema titles: usd_url is 'URL or local path', position is '[x, y, z] world position', scale is '[sx, sy, sz] scale factors', and prim_path is the target prim. This compensates for the 0% schema description coverate. However, command_id and idempotency_key are completely omitted, leaving their purpose unexplained.

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 opens with 'Load a USD asset from a URL or file path into the scene' – a specific verb (Load), resource (USD asset), and source. It clearly distinguishes this tool from siblings like load_environment or generate_3d, which do not target URL/path USD assets.

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 when-to-use guidance is provided. The description never names alternative tools or states conditions for choosing this one over siblings such as load_environment or search_usd. An agent receives no information about when this tool is preferable.

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