get_usd_bound_material

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only query, but says nothing about what 'where the binding comes from' yields (e.g. which layer or composition arc), whether unbound prims are omitted or reported as null, or how heavy the traversal is across many prim_paths.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is a symptom of under-specification rather than disciplined editing.

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?

With no annotations, no output schema, and zero schema description coverage on three parameters, the definition leaves the agent guessing about inputs and return shape. For a query that fans out over multiple prim paths, this is substantially under-described.

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 0% and three parameters (node_path, prim_paths, purpose with default 'full') are entirely undocumented. The phrase 'each prim' faintly implies prim_paths is a list, but nothing explains node_path or what the 'purpose' values mean, so the description fails to compensate for the coverage gap.

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 and resource: return the material bound to each prim, plus the provenance of that binding. This is meaningfully more specific than sibling names like get_usd_materials or get_material_info, though it never explicitly contrasts itself with them.

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?

There is no guidance on when to choose this over get_usd_materials, get_usd_material_textures, or get_material_info, and no stated preconditions such as requiring a loaded stage or resolved layers. The agent must infer the use case from the verb alone.

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