rhino_subd_loft

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

With no annotations, the description must carry behavioral disclosure. It communicates that the tool creates a new SubD loft from selected curves and that closed means periodic, but says nothing about prerequisites, failure modes, or side effects beyond creation. This is adequate but thin.

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 sentence is front-loaded and the parameter notes are compact. No filler or redundant information; every line earns its place.

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 one-parameter tool with an output schema, this is close to complete, but it leaves the selection requirement implicit and doesn't specify how the chosen curves are provided or validated. A short explicit usage note would make it fully self-contained.

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 descriptions are absent, so the description compensates by explaining 'closed' as creating a closed/periodic loft. It also documents a 'controller' argument, though this is not present in the schema, which is slightly confusing.

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?

States a specific action ('Create a SubD loft surface') and resource ('through selected curves'), clearly distinct from general loft and SubD primitives. It doesn't explicitly call out sibling tools like rhino_subd_sweep1/2, so it's clear but not fully differentiated.

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 curves' implies the tool should be invoked after selecting curves, and 'closed' describes an option. However, there is no explicit when-to-use guidance, no exclusions, and no alternatives mentioned, leaving selection to inference.

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