Activates radial dimension placement mode in Rhino, letting you add radius measurements to arcs and circles. Use it when you need to place radial dimensions in the model.
Enter radial (radius) dimension placement mode.
| 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 carries the full burden of explaining behavior. It indicates the tool enters a placement mode, but it does not disclose that this is likely an interactive operation requiring user input, whether it creates an object, or what the tool returns. The behavioral surface is therefore largely unspecified.
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, front-loaded sentence with no filler or repetition. It communicates the core action efficiently and is appropriately sized for a tool with no parameters.
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 parameterless tool, the description covers the basic purpose adequately. However, it omits important context about the interactive nature of dimension placement mode, what the user or agent should expect after entering the mode, and whether any geometry selection is required first. The output schema exists, but behavioral context is still thin.
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 tool has zero parameters and the input schema is empty, so there is nothing for the description to add about parameter semantics. The baseline for zero-parameter tools is 4, and no deduction is warranted.
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 and resource: it enters radial/radius dimension placement mode. This clearly distinguishes it from sibling dimension tools like linear, aligned, angular, and ordinate dimensions. It stops short of a 5 because it does not explicitly name those alternatives, but the purpose is unambiguous.
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?
There is no guidance about when to use this tool versus other dimension tools such as rhino_add_dimension_linear or rhino_add_dimension_angular. The description only states what the mode is, leaving the agent to infer when it should be invoked. No exclusions, prerequisites, or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.