rhino_fair_curve

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

With no annotations present, the description carries the full burden of behavioral disclosure. It mentions the pre-selection requirement and the return dict, but it does not state whether the curve is modified in place, whether the operation is destructive, or what happens if no valid curve is selected. This is a significant gap for a command that mutates geometry.

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 brief, front-loaded with the action, and uses compact Args/Returns blocks. Every sentence contributes necessary information with no filler.

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 zero-parameter tool, the mandatory pre-selection condition and the basic return shape are stated. However, the description leaves ambiguity about whether the FairCrv command is actually executed or only a command string is returned, and it does not clarify the mutation effects on the selected 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 input schema has zero parameters, so there is little for the description to explain; the baseline is 4. The description does mention the controller argument, which clarifies the expected calling convention even though the schema does not list it.

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 and resource: 'Fair (smooth) the selected curve' using Rhino's FairCrv command. It clearly identifies the operation and distinguishes it from general curve-editing siblings like rhino_smooth or rhino_rebuild_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?

The description explicitly states that the curve must be pre-selected before calling, which is a clear usage precondition. However, it does not explain when to prefer this tool over related alternatives such as rhino_smooth or rhino_rebuild_curve, nor does it provide any exclusions.

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