configure_body_material

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Configure' and never states whether this mutates the selected object's material, creates or replaces a material, has prerequisites, or returns anything. This is a significant gap for an apparent mutation tool.

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 short, front-loaded with its purpose, and the supported-use line earns its place. The Args block is conventional and contains no filler.

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 material-mutation tool with no annotations and no output schema, the description omits side effects and prerequisites. An agent can infer parameter meanings but not what happens when the tool is called, making it incomplete for reliable invocation.

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 is the only source of parameter meaning. It gives one-line meanings for all four parameters, and color and metallic receive useful ranges, but material_name and roughness are mostly restatements of their names.

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 uses a specific verb ('Configure') and a clear resource ('solid body/casing material'), with the 'solid opaque surface' scope helping separate it from glass/display material siblings. It does not explicitly name sibling tools, but the resource and qualifier are distinct enough.

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 'Works for product casings, furniture surfaces, architectural elements' sentence gives application context, but there is no explicit guidance on when to prefer this over assign_material, set_material_property, create_material, or configure_display_material. No exclusions or alternatives are mentioned.

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