apply_material

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It communicates that this is a binding/mutation operation but does not explain whether existing bindings are replaced, whether changes persist, what side effects occur, or whether any permissions are needed.

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 concise and well structured: a clear one-sentence purpose followed by a compact args list. There is no filler and all information is relevant.

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?

The core parameters are covered and an output schema exists, so return value details are not needed. However, with no annotations, the lack of side-effect disclosure and relationship to related material tools leaves the context incomplete for an agent making routing or safety decisions.

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 the description compensates well for the three core parameters by explaining material_path, target_prim_path, and material_purpose values. It omits the auxiliary command_id and idempotency_key parameters, but these are generic and less critical for correct invocation.

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 an unambiguous action: 'Bind a material to an object.' It clearly identifies both the resource being applied and the target, and it is easily distinguished from sibling tools like create_material and get_material_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 tool's usage is implied: it is used when a material and a target object prim already exist. However, it does not explicitly state when to prefer this over alternatives like get_material_binding, nor does it give exclusions or prerequisites.

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