get_usd_bound_material

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

With no annotations provided, the description carries the full burden. It discloses important behavior: resolution follows ComputeBoundMaterials, missing material prims are reported in 'missing_material' rather than as unbound, and the 'purpose' fallback behavior. It also notes batching ('pass every prim of interest in one call'). It does not mention performance or error cases beyond missing materials, but the key behavioral traits are covered.

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 and front-loaded with the core semantics, then the batching note, then parameter docs. Every sentence earns its place. The only minor issue is that the parameter docs are formatted as an Args block, which is slightly redundant with the schema but still adds value.

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 read-only query tool with 3 parameters and no output schema, the description covers the essential context: what is returned, how bindings are resolved, the missing-material edge case, and the purpose options. It does not describe the exact return structure (e.g., field names beyond 'missing_material'), but the absence of an output schema makes that a minor gap.

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%, so the description must compensate. It explains node_path as the LOP node whose stage to read, prim_paths as the prim paths to resolve, and purpose with its three values and their meanings. This adds real meaning beyond the bare schema titles, though it could be more explicit about the exact format of prim_paths (e.g., absolute vs relative).

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 states a specific verb ('get'), a precise resource ('the material each prim renders with'), and the resolution semantics ('ComputeBoundMaterials'). It also distinguishes the binding source (direct/inherited/collection) and the missing-material case, which clearly separates it from sibling tools like get_usd_materials or list_materials.

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 description gives clear context on when to use the tool: to resolve the material a prim actually renders with, including inherited and collection bindings. It also explains the 'purpose' parameter's role in choosing what Karma renders. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough for an agent to select it appropriately.

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