get_material_binding

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

No annotations are provided, so the description carries the behavioral burden. It does disclose that the operation is a read and that the binding is 'resolved', which adds meaningful nuance, but it does not explain what 'resolved' means in terms of traversal or fallbacks, nor what happens when no binding exists.

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?

One concise sentence with the verb and object front-loaded, no filler or repetition. It could have added a bit more usage context without becoming bloated, but as written it is efficient and scannable.

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 simple read tool with an output schema, the description covers the core action and target resource, but it does not fully explain how to request visual vs physics bindings via material_purpose or what 'resolved' entails. Given the presence of an output schema, return-value documentation is unnecessary, but parameter-level context is still thin.

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 for undocumented parameters. It adds meaning to target_prim_path ('on a prim') and partially to material_purpose ('physics or visual'), but it leaves command_id and idempotency_key entirely unexplained and does not explicitly map the 'physics or visual' wording to the parameter values.

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 ('Read') and resource ('resolved physics or visual material binding on a prim'), making the operation clear. The phrase 'on a prim' also distinguishes it from sibling get_material, which is likely about the material itself rather than the binding.

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 clearly implies this is the tool to use when you need a prim's material binding, but it gives no explicit guidance about when to choose it over closely related siblings such as get_material or apply_material. It names no alternatives, exclusion conditions, or precedence rules.

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