rhino_material_create

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

Annotations already signal a mutating operation via readOnlyHint false, and 'Create' matches that. However, the description adds no extra behavioral context such as duplicate-name handling, document targeting via doc_id, or whether the material remains unassigned after creation. It is not contradictory, but it provides no additional transparency.

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?

One compact, front-loaded sentence with no filler. Every word earns its place, and the key resource-verb pair appears immediately.

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 relatively simple creation tool with a detailed schema and output schema, the description is minimally adequate. But it relies on the schema for the required name, doc_id default, and value constraints, while leaving the relationship to material_assign and material_preset_create implicit.

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 should compensate. It maps three appearance concepts to parameters — diffuse, transparency, glossiness — but omits the required name parameter and the doc_id document-targeting parameter, and gives no interpretation of the 0-1 value ranges.

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 and resource: 'Create a material' plus the three key appearance fields. This clearly distinguishes it from sibling tools like material_assign or material_preset_create by focusing on the creation of a stand-alone material definition.

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?

There is no guidance on when to use this tool over closely related siblings such as rhino_material_assign, rhino_layer_set_material, or rhino_material_preset_create. The description states the action but provides no conditions, exclusions, or alternatives.

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