rhino_to_nurbs

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Convert selected SubD objects' but does not explain whether the operation creates new objects, modifies originals, requires an active selection, or has any side effects in the Rhino document.

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 purpose is stated in one concise, front-loaded sentence. The extra 'Args' line is largely unnecessary since the schema declares no parameters, but the overall description remains short and readable.

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?

For a zero-parameter tool with an output schema, a brief description may be adequate, and this one covers the core operation. However, it omits selection preconditions, what happens if no SubD objects are selected, and why an agent should choose this over rhino_subd_to_nurbs.

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 no user parameters need semantic explanation. The description's 'Args: controller: RhinoController instance' line is not reflected in the schema and reads like internal documentation, but it does not create a meaningful parameter ambiguity given the empty schema.

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 the operation: convert selected SubD objects to NURBS surfaces. It identifies both the input object type and the output type, which differentiates it from mesh conversion tools like rhino_mesh_to_nurbs. However, it does not distinguish itself from the very similar sibling rhino_subd_to_nurbs.

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?

No usage guidance is provided. It does not say when to prefer this tool over rhino_subd_to_nurbs, rhino_mesh_to_nurbs, or rhino_to_subd, nor does it state prerequisites such as requiring a current Rhino selection of SubD objects.

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