rhino_material_preset_create

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

The description meaningfully discloses mode-dependent behavior beyond the annotations: standalone mode produces only a basic rhino3dm material, while Bridge mode adds PBR render content and IOR. This helps an agent predict output differences. It does not contradict the readOnlyHint=false annotation.

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 compact and front-loaded with the core purpose. The second sentence adds only the useful mode distinction without filler or redundant phrasing.

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?

The core purpose and mode split are covered, and the schema handles parameter details and return structure. However, the description does not explain what triggers Bridge mode, nor does it mention that preset names come from rhino_material_preset_list as a prerequisite step. This leaves some contextual ambiguity for an agent.

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 description itself does not elaborate on parameters, but the input schema already provides useful descriptions for doc_id, preset_name, and material_name, including defaults and the relationship to rhino_material_preset_list. The description adds little beyond the schema, so a baseline score of 3 is appropriate.

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 first sentence clearly identifies the action: creating a document material from a bundled physical preset. It is specific about the resource and operation, though it does not explicitly differentiate itself from sibling tools like rhino_material_create.

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 explicit guidance on when to use this tool versus alternatives such as rhino_material_create or rhino_material_preset_list. The mention of 'bundled physical preset' implies the use case, but the description does not state prerequisites, exclusions, or routing conditions.

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