rhino_set_object_material

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation assigns a material but does not reveal whether existing material assignments are overwritten, whether the material is created if missing, how the tool behaves with no selection, or whether the action is reversible.

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 and front-loaded with the core action, making it easy to scan. The Args block is somewhat redundant given the schema already defines material_name, but it does not introduce meaningful bloat.

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?

Although the tool is simple with a single parameter, the description lacks important operational context: selection is a stated requirement but not framed as a precondition, the relationship to material creation is unclear, and the abundance of material-related sibling tools makes the lack of differentiation a real usability gap.

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 schema provides zero description coverage for material_name, and the description only repeats the parameter name with the phrase 'Name of the render material.' It adds no guidance about valid values, whether the material must already exist in the document, naming conventions, or how the parameter maps to a specific material.

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 clear verb ('Assign') and resource ('named render material to currently selected objects'), so an agent can tell what action is performed. However, it does not differentiate itself from closely related sibling tools like rhino_material_assign or rhino_assign_material_to_object, which appear to serve the same or overlapping purpose.

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 indicates the operation applies to 'currently selected objects,' which gives some usage context, but it provides no guidance on prerequisites (objects must be selected), whether the material must already exist, or when to prefer this tool over material-related siblings. No alternatives or exclusions are mentioned.

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