rhino_create_subd

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

Annotations only provide a title, so the description carries the full burden of behavioral disclosure. It states the creation action but does not describe whether the source mesh is modified or left intact, whether any conversion tolerance or settings affect the result, or what happens to existing SubD data. This is minimal behavioral coverage for a mutation-style 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, tightly worded sentence that front-loads the primary action and input type. No filler words or redundant details are present; it earns its place even if it is minimal overall.

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?

Given the tool's moderate complexity and the lack of substantive annotations, the description is not complete enough for an agent to confidently choose and invoke it. It omits when to use it versus similar conversion tools, behavioral side effects, and parameter semantics. The presence of an output schema partially covers return expectations, but the other gaps remain significant.

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?

With schema description coverage reported at 0%, the description needed to compensate by explaining parameters, but it only echoes the source-mesh relationship already implied by the tool name. It adds no meaning for the `name`, `layer`, or `interpolate_corners` parameters, and only weakly maps to `mesh_id` as 'existing mesh.'

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 and resource: 'Create a SubD object from an existing mesh.' This clearly differentiates from primitive SubD creators like rhino_subd_box or rhino_subd_sphere, which do not require an existing mesh. However, it does not explicitly distinguish itself from the similar-sounding sibling rhino_to_subd, leaving some ambiguity.

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 implies usage when the user has an existing mesh to convert into a SubD, but it provides no explicit guidance about when not to use this tool, nor does it mention alternatives such as rhino_to_subd or SubD primitive creation tools. The usage context is inferable but not directly stated.

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