configure_display_material

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

With no annotations, the description carries the behavioral disclosure burden. It explains that the tool sets dark base color, low roughness, and optional emission, and gives meaningful scale info for emission strength. However, it does not state whether the material must already exist, whether existing values are overwritten, or what the return/side effects are.

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 tightly structured: a one-line purpose, a short behavior summary, usage examples, and a compact Args block. Every sentence adds value, and the core purpose is front-loaded.

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 tool with five optional parameters and no output schema, the description covers parameter meaning, defaults, and typical usage. The main gap is lack of clarification around creating vs. modifying materials, and no comparison to set_material_property or configure_glass_material.

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 fully compensates. Every parameter is given a semantic explanation: material_name, color range (0-1), roughness meaning (0.03 = mirror-like), emission_color, and emission_strength scale (0 = off, 1+ = glowing). This enables correct invocation despite the bare schema.

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 a specific verb and resource: 'Configure a display/emissive material.' It further clarifies scope with concrete examples like phone screens, monitors, TVs, and HUDs, distinguishing it from sibling material tools such as configure_glass_material and configure_body_material.

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 indicates when this tool is appropriate: for any emissive/display surface. It does not explicitly name alternatives or exclusion conditions, but the use case is unambiguous enough to guide tool selection.

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