set_material

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

No annotations are provided, so the description carries full burden. It explains parameter ranges (e.g., 0-1 for colors, 0=dielectric, 1=metal for metallic) but does not disclose side effects like whether it replaces the entire material or just modifies properties, or if it creates a new material when none 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?

The description is two sentences: a clear purpose statement followed by a parameter list. It is front-loaded and concise, though the parameter list is a bit run-on and could benefit from bullet points or clearer separation.

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?

Given 14 parameters and no annotations or output schema, the description explains the most critical parameters but omits details on ior, specular, clearcoat, subsurface, alpha, sheen, and the required 'name' parameter. It covers enough for basic use but is not fully comprehensive.

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?

With 0% schema description coverage, the description adds significant meaning to key parameters: base_color (RGB[A] 0-1), metallic (0/1), roughness (0-1 mirror/diffuse), transmission (0 opaque/1 glass), and emission_color/strength. However, parameters like ior, specular, clearcoat, subsurface, alpha, and sheen are not explained.

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 clearly states the tool's action: 'Set PBR material properties on an object using Principled BSDF.' It specifies the verb 'Set' and the resource 'PBR material properties on an object', and distinguishes it from siblings like 'set_principled_bsdf' or 'material_create_pbr' by focusing on setting multiple material parameters in one call.

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 lacks explicit guidance on when to use this tool versus alternatives such as 'set_principled_bsdf', 'material_create_pbr', or 'material_assign'. It does not specify prerequisites (e.g., object must have a material already) or scenarios where this tool is preferred.

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