rhino_create_material

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

Annotations provide no safety hints (all false), so the description must carry behavioral details. It only states the action (create) without elaborating on side effects, such as whether existing materials are affected, naming conflicts, or that the material is stored in the material library. This is minimal beyond what the name implies.

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?

A single sentence that is front-loaded with the action and resource. Every word is necessary; there is no fluff or redundancy.

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 create operation with a detailed schema and an output schema (per context), the description is minimally adequate. However, it does not explain that a new material is created independently of objects, nor does it clarify the relationship to sibling tools like rhino_assign_material. Some contextual guidance is missing.

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?

The nested schema already provides detailed descriptions for all parameters (name, diffuse_color, ior, reflectivity, transparency) with ranges and defaults. The tool description adds no additional parameter information, but the schema does the heavy lifting, so a baseline of 3 applies despite the context signal indicating 0% coverage (which appears to be miscalculated for the top-level 'params' only).

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 action (create) and resource (render material) and lists key properties (color, transparency, reflectivity). It is clear and distinct from siblings like rhino_assign_material or rhino_set_material, though it does not explicitly name those alternatives.

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?

No guidance on when to use this tool versus alternatives. It does not mention that this creates a material in the document as opposed to assigning an existing one or setting material properties on an object. No exclusions or prerequisites are given.

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