get_usd_bound_material

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: renderer-equivalent resolution semantics, the three binding-source outcomes (direct/inherited/collection), and the missing_material edge case. It does not state the response shape or that the operation is a safe read, but for a getter it covers the non-obvious behavior well.

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?

Front-loaded with the core semantics before the Args block, and every sentence adds information. Slightly dense prose ('resolved the way the renderer resolves it') costs a little, but nothing is wasted.

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?

No output schema and no annotations, so the description must explain returns, and it does name the important result fields (binding source, missing_material). It stops short of describing the material value format itself, leaving a small gap for a resolution tool.

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 coverage is 0%, so the description must compensate, and it does: node_path and prim_paths are glossed, and purpose is explained in detail with its default and the meaning of 'full', 'preview' and 'all'. The purpose values are not registered as an enum in the schema, so this text is the only place the accepted values are defined.

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+resource (resolve the material each prim renders with) and pins the exact semantics via ComputeBoundMaterials, distinguishing it from siblings like get_usd_materials, list_materials and get_material_info. An agent can tell it apart without opening the schema.

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 'Batched: pass every prim of interest in one call' line gives practical invocation context, and 'full' is flagged as the default. However, there is no explicit when-to-use-vs-alternative guidance (e.g. versus get_usd_materials or list_materials), so the routing is only implied.

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