rhino_network_surface

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

The description only says 'build a surface', which aligns with the readOnlyHint=false annotation (it creates something). No additional behavioral details such as failure cases, temporary effects, or permissions are given.

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 short sentence that immediately conveys the core function. It is efficiently front-loaded and contains no fluff.

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 complexity of creating a surface from a curve network, the description lacks critical context: expected curve configuration, handling of non-network curves, output details, or error conditions. The output schema exists but the description does not compensate for the missing 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% for the main args parameter, and the description does not explain what the parameters are or how to structure the network. It adds no meaning beyond the schema.

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 specifies the verb 'Build' and the resource 'surface from a network of crossing curves', making it clear and distinct from sibling surface creation tools like loft, sweep, or extrude.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, no scenario exclusions. It simply states the operation.

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