Unjoin selected edges from a polysurface to modify them independently without affecting the whole surface.
Un-join selected edges from a polysurface.
Args:
controller: RhinoController instance.
Returns:
Dict with command result.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It states the action but does not disclose side effects, reversibility, or any impact on the selection or document state, which is important for a modifying operation.
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 concise, consisting of a single purpose sentence plus a brief list of arguments and return type. It is not overly verbose and conveys the necessary information without extraneous text.
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 description includes the return type ('Dict with command result') and identifies the controller argument, which helps set context. However, it lacks details about error conditions, selection requirements, or any expected side effects, leaving some ambiguity for a complex Rhino operation.
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 indicates zero parameters, but the description mentions an 'Args: controller: Rhino instance' parameter, creating a contradiction. The description adds information that conflicts with the schema, confusing the agent about whether a controller argument is required.
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 clearly states a specific action ('Un-join') on a specific resource ('selected edges from a polysurface'), making the tool's purpose immediately understandable and distinguishable from other edge-related tools in the sibling list.
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 that the tool operates on the current selection in Rhino, but it does not explicitly state when to use this tool versus alternatives like rhino_split or rhino_merge_edge, nor does it mention any prerequisites (e.g., edges must be selected).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.