rhino_material_preset_create

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

The description explains the behavioral difference between standalone (basic Material) and bridge mode (PBR render content + IOR), adding context beyond the readOnlyHint=false annotation. It discloses what kind of material is produced, which is useful for agent decision-making.

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 concise at three sentences, front-loading the core purpose. It uses line breaks for readability and avoids unnecessary repetition. Each sentence earns its place.

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?

Given the tool's complexity (with modes and output schema) and the availability of sibling tools like rhino_material_preset_list, the description is fairly complete. It explains the two modes and their output differences, though it could briefly mention that the preset_name should come from the list tool.

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 descriptions cover all parameters (doc_id, preset_name, material_name) with clear explanations. The description does not add additional detail about parameters beyond what the schema provides, but schema coverage is high, so the baseline 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 description clearly states it creates a document material from a bundled physical preset, specifying the resource and action. It distinguishes standalone vs bridge modes but does not explicitly differentiate from sibling tools like rhino_material_create, which could also create materials.

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 mentions standalone and bridge modes but provides no explicit guidance on when to use this tool versus alternatives (e.g., rhino_material_create) or when not to use it. No exclusion criteria or context for selection.

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