rhino_subd_to_nurbs

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

The annotations provide only a title, so the description carries the full behavioral burden. It states the output type but does not disclose whether the original SubD is preserved, replaced, or deleted, nor does it mention side effects like object creation, selection changes, or packing behavior. This is a meaningful gap for a conversion tool.

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 a single efficient sentence with no filler or repeated information. It is slightly under-specified, but structurally it is concise and front-loaded.

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?

The description is too thin for a tool with no behavioral annotations and multiple parameters. It does not explain the required object_id input, what happens to the original SubD, or how the optional parameters affect the result. The output schema reduces the need to describe return values, but the side effects and selection context remain unclear.

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 description adds no parameter-level meaning beyond the schema. The input schema already explains object_id and packed, but name and layer are left undocumented in both the schema and description. With schema description coverage low, the description does not compensate.

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 names a specific verb ('Convert'), source ('a SubD object'), and result ('a NURBS polysurface (Brep)'), making the core operation clear. It does not explicitly differentiate this from sibling conversion tools like rhino_to_nurbs, though the source/target types in the description imply the distinction.

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?

Usage is implied: use this when a SubD object needs to become a NURBS Brep. However, the description gives no explicit when-to-use or when-not-to-use guidance, and does not mention alternatives such as rhino_mesh_to_nurbs or rhino_to_nurbs.

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