rhino_isocurve

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

There are no behavioral annotations beyond a title, and the description does not disclose whether this operation creates a new curve object, modifies the surface, or simply returns data. For a geometry extraction tool this side-effect ambiguity is significant.

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?

One sentence, front-loaded with the core action and resource, and no filler. It is appropriately succinct for this tool.

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?

The schema and output schema carry much of the technical detail, and the description captures the core operation. However, with no annotations and no mention of side effects or required preconditions, the definition is adequate but not fully complete for an autonomous agent.

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 schema already documents object_id, parameter, and direction, including the 0=U-direction and 1=V-direction mapping. The description adds no new parameter semantics beyond restating that the isocurve is U/V-based, so the baseline of 3 applies.

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 uses a specific verb ('Extract') and resource ('an isocurve from a surface') and identifies the key input ('a specific U or V parameter'). This clearly distinguishes the tool from related surface query tools such as rhino_evaluate_surface or rhino_surface_closest_point.

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 does not state when to prefer this tool over alternatives, nor does it give exclusions or prerequisites. Usage context is only implied by the name and one-liner, so an agent gets no explicit routing guidance.

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