set_material

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds that a material is created automatically and bound to the prim, plus color auto-detection, but it does not say what happens to an existing bound material or whether the operation can be undone.

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?

Three short sentences, front-loaded with the action and resource. The material auto-creation detail follows logically; 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?

With a full schema, an output schema, and annotations covering safety, the description only needs to explain the material-creation/binding behavior. It does that adequately, though it could note whether existing material bindings are replaced.

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 100%, so all six parameters are documented in the schema, including color ranges, opacity, metallic, roughness, and material_path default behavior. The description's note about 0-1 floats versus 0-255 ints repeats what the schema already states, so it adds little beyond baseline.

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: applies an OmniPBR PBR material to a prim with color and surface properties. It is clearly a material-assignment tool, distinct from scene-inspection or transform siblings, though it does not explicitly contrast with update_material_paths.

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?

Usage is implied by 'Apply a PBR material... to a prim', but there is no explicit when-to-use guidance, no prerequisites, and no named alternative such as update_material_paths. An agent must infer when this is the right sibling.

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