rhino_edit_points_on

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

With no annotations, the description carries the behavioral burden. It clearly signals a non-destructive display operation ('edit point display'), and scopes the effect to selected curves or surfaces. However, it does not disclose whether the display state persists, whether it only affects the current document session, or whether selection is required.

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 clear sentence with no filler. It front-loads the action and immediately identifies the target objects.

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 display toggle, the description is sufficient for an agent to invoke it. An output schema exists, so return-value details are not required. It could be slightly stronger with an explicit note that it applies to the current Rhino selection.

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 is empty, so there are no parameters to document. The description does not need to add parameter details, matching the baseline for a zero-parameter tool.

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 ('Turn on') and names the resource ('edit point display for selected curves or surfaces'). It is clearly distinct from siblings like rhino_points_on and rhino_edit_points_off, though it does not explicitly name an alternative.

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 implies the tool is for turning on edit point display on selected curves or surfaces, but it gives no explicit when-to-use guidance or comparison with related tools such as rhino_points_on, rhino_edit_points_off, or rhino_add_control_point. No exclusions or prerequisites are mentioned.

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