Save the active Rhino model to its existing file path to persist changes without prompting for a location.
Save the current document to its existing file path.
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 carries the full burden of behavioral disclosure. It indicates the target is an existing file path, implying overwrite behavior, but it does not explicitly state that the file will be overwritten, whether a prompt may appear, or what happens if the document has never been saved. For a state-changing operation, this is a meaningful transparency gap.
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 short and front-loads the core purpose in the first sentence. The Args and Returns sections are minimal but conventional; the controller line adds little value and the return description is vague, but overall the structure is clean and efficient.
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?
This is a simple operation and an output schema exists, so full return-value documentation is not strictly needed. Still, the absence of annotations and the lack of explicit overwrite/error context means the description is only minimally complete for an agent that must decide when and how to invoke 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?
The input schema has zero parameters, so there is nothing for the description to document at the schema level. However, the description mentions 'controller: RhinoController instance,' which is not reflected in the schema and is not an actionable user-facing parameter; this slightly muddies the parameter story rather than adding useful semantics.
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 clear action and target: 'Save the current document to its existing file path.' This makes the tool's purpose immediately understandable. However, it does not explicitly distinguish itself from closely related siblings like rhino_save, rhino_save_as, and rhino_save_copy, so it misses full sibling differentiation.
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 phrase 'existing file path' implies this is for saving without a file dialog or new path, which gives some usage context. There is no explicit guidance on when to choose this tool over rhino_save, rhino_save_as, or rhino_save_copy, so usage guidance is only implied rather than clearly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.