rhino_subd_to_nurbs

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

Annotations provide only a title; no readOnlyHint or destructiveHint. Description does not disclose whether the original SubD is modified, if a new object is created, or other side effects.

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?

Single sentence is efficient and front-loaded, but could benefit from slight expansion to include parameter hints or usage context.

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 simple conversion tool, basic context is present. However, missing behavioral details and lack of guidance relative to sibling tools leaves gaps for new users.

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 includes descriptions for 'packed' and 'object_id' but not for 'name' and 'layer'. The tool description adds no parameter context, leaving users to infer meaning from schema alone.

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?

Description states 'Convert a SubD object to a NURBS polysurface (Brep)', which clearly specifies the action and output. This distinguishes it from sibling tools like mesh conversion or surface creation.

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 guidance on when to use this tool versus alternatives (e.g., rhino_mesh_from_surface, rhino_create_subd). No prerequisites or disclaimers provided.

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