rhino_flow_along_curve

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

The description only says 'reposition', but does not disclose whether original objects are modified, whether copies are created by default, whether undo is supported, or what side effects occur. With no behavioral annotations provided, this is a significant transparency gap.

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 concise sentence with no filler or redundant wording. It is well-structured and easy to parse.

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 geometry transformation tool with multiple nested parameters and a copy option, the description is too sparse. It does not explain required inputs, the meaning of object_ids, how make_copy behaves, or any constraints on the base/target curves.

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 provides descriptions for base_curve_id and target_curve_id, but object_ids and make_copy lack meaningful descriptions. The tool description adds no parameter clarification, and the top-level 'args' wrapper with nested fields is not explained.

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 clear action ('Reposition objects') and the geometric relationship (base curve to target curve). It is sufficiently specific to the tool's function, though it does not explicitly differentiate itself from similar sibling tools like rhino_flow or rhino_cmd_flow_along_curve.

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?

Provides no guidance on when to use this tool versus alternatives such as rhino_flow, rhino_cmd_flow_along_curve, or rhino_array_on_curve. Missing any context about prerequisites, copy behavior, or selection requirements.

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