rhino_assign_material_to_object

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a mutating operation and clarifies scope ('currently selected objects'), but it does not disclose behavior when nothing is selected, whether the material must already exist, whether existing assignments are overwritten, or any error conditions.

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 two sentences, front-loaded with the core purpose before the parameter detail. Every sentence earns its place, and there is no filler or unnecessary repetition.

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?

This is a simple one-parameter mutation, and the description covers purpose, selection scope, and parameter semantics. However, with no annotations and no usage guidance relative to overlapping siblings, important operational details such as selection requirements, material existence, and overwrite behavior are missing, making it only minimally viable.

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 must compensate. It does by explaining 'material_name: Name of the render material to assign,' which adds the important 'render material' context beyond the raw parameter name. It could mention existence or format requirements, but for a single string parameter this is mostly adequate.

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 verb ('Assign'), a resource ('a named material'), and a target ('currently selected objects'). It is clear and unambiguous, but it does not distinguish itself from overlapping sibling tools such as rhino_material_assign or rhino_set_object_material.

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 provides no explicit guidance on when to use this tool versus alternatives. It implies the precondition that objects are selected and a material name is required, but it does not reference sibling tools or state any exclusions.

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