rhino_loft

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

Annotations already carry readOnlyHint: false, so the agent knows this is a mutating operation; the description adds that it consumes profile curves and produces a surface, which is consistent. However, it doesn't disclose behavioral nuances such as sensitivity to curve ordering, whether the source curves remain unmodified, or how loft_type affects the result. No contradiction with annotations.

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?

A single 10-word sentence, front-loaded with the verb, zero filler or repetition. Every word earns its place, and the statement is immediately scannable.

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?

This is a nuanced surface-creation tool with 6 parameters, including loft_type with 5 modes and a closed flag, yet the description is only one sentence. It fails to address curve ordering requirements, what the loft_type presets mean, when closed is appropriate, or how this tool relates to the dozens of surface-creation siblings. The output schema and annotations do not compensate for this lack of guidance.

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 description coverage is 0%, so the description carries the burden. It usefully clarifies the core parameter profile_ids as 'profile curves,' which is meaningful. But it adds nothing about name, layer, closed, or loft_type semantics beyond what the schema's terse titles and defaults already show, leaving half the tool's behavior unexplained.

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 verb ('Loft'), a specific input ('a sequence of profile curves'), and a clear output ('a surface'). This is a functional definition that an agent can act on. However, it doesn't differentiate from siblings like rhino_cmd_loft, rhino_subd_loft, rhino_sweep1, or rhino_network_surface, all of which also create surfaces from curves.

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?

There is no guidance on when to use loft versus the many alternative surface-creation tools in the sibling list (sweep1/sweep2, network_surface, patch, edge_srf, subd_loft). The description provides no exclusions, no prerequisites, and no hint about which scenario favors lofting over other operations, leaving the agent to guess.

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