rhino_set_control_points

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

Annotations provide no behavioral hints. Description says 'Replace' implying mutation, but does not disclose side effects, undo behavior, or whether the original object is modified in place. With no annotations, description should offer more context.

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?

Single sentence that is concise and to the point. No unnecessary words, but could be expanded with additional context without becoming verbose.

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?

Description lacks information about return value, constraints (e.g., point count must match), and whether the operation modifies the object or returns a new one. Output schema exists but description does not complement it.

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 provides good descriptions for all parameters (points, weights, object_id). The description adds no extra meaning beyond the schema. Baseline 3 applies due to high schema description coverage.

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?

Description clearly states the action 'Replace control points' and the target 'NURBS curve or surface'. The name 'set_control_points' aligns with the purpose and distinguishes from sibling 'rhino_get_control_points'.

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 explicit guidance on when to use this vs. alternatives like 'rhino_rebuild_curve' or 'rhino_match_surface'. No mention of prerequisites or when not to use. Usage is only implied by the description.

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