rhino_nurbs_curve

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

The description states 'Add', consistent with readOnlyHint=false, but adds no behavioral details beyond what annotations already imply. It does not disclose side effects, permission requirements, or creation behavior (e.g., auto-layer creation is in schema, not description).

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 sentence with zero waste. It is efficiently structured and front-loaded with the key action and resource.

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 has multiple parameters and an assumed output schema, the description lacks sufficient context. It does not explain what a NURBS curve is, why control polygon method is used, or how it differs from similar tools like rhino_interpolate_curve.

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?

The tool description does not mention any parameters. Although the input schema provides thorough descriptions for all sub-parameters (name, layer, degree, doc_id, control_points), the description itself adds no semantic value to help the agent understand parameter usage.

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 'Add a NURBS curve from a control polygon' uses a specific verb ('Add'), resource ('NURBS curve'), and source ('control polygon'). This clearly distinguishes it from sibling curve creation tools like rhino_interpolate_curve or rhino_line.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or typical use cases, leaving the agent without context to choose correctly among related tools.

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