rhino_mesh_to_nurbs

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only names the operation and does not explain whether the original meshes are preserved, deleted, or hidden, what happens with no selection, or whether the conversion 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 main sentence is concise and front-loaded, but the trailing 'Args: controller' boilerplate adds no value and is inconsistent with the empty input schema.

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 zero-parameter conversion tool and an output schema is present, so the core intent is clear. Still, the behavior around the original meshes and selection requirements is not described, leaving notable gaps 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 input schema has zero properties, so there are no real parameters. The description still lists a 'controller' argument in its Args section, which is not present in the schema and creates ambiguity rather than adding meaningful parameter guidance.

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 ('Convert selected mesh objects to NURBS surfaces') with a clear resource and transformation. It differentiates the tool from related siblings like rhino_subd_to_nurbs and rhino_mesh_from_nurbs without needing to open their schemas.

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 phrase 'selected mesh objects' implies the tool operates on a current selection, which gives some usage context. However, it does not explicitly state when to prefer this over other conversion tools, nor does it mention exclusions or prerequisites.

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