set_material_properties

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

No annotations exist, so the description carries the burden of behavioral disclosure. It explains the recompile parameter default and lists acceptable values for blend_mode and shading_model, but does not mention side effects, permissions, or what happens to other properties not specified.

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 with a one-line purpose statement followed by parameter details. However, the parameter list is not formatted as a clear bullet list, slightly reducing readability. It is front-loaded and efficient.

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 8 parameters, no annotations, and an output schema (not shown), the description should fully explain the tool's behavior. It only details 2 parameters and omits the effects of omitted properties. It also lacks guidance on how this compares to sibling material tools, leaving the agent underinformed.

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 covers blend_mode and shading_model with possible values and mentions recompile, but leaves 5 other parameters (two_sided, dithered_lof_transition, etc.) unexplained. This is insufficient for a tool with 8 parameters.

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 'Bulk-set material-level properties in one call', specifying a verb (set) and resource (material properties), and distinguishes from sibling tools like set_material_instance_parameter by emphasizing bulk-setting at the material level.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or which sibling tools handle similar tasks (e.g., set_material_instance_parameter).

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