Create a backup copy of the open SketchUp model before risky edits; it saves alongside the original with a default timestamp suffix and leaves the current file unchanged.
Save a copy of the model alongside the original as '_.skp', leaving the open file untouched. Defaults the suffix to a timestamp. Use this to take a backup before a risky batch of edits.
| Name | Required | Description | Default |
|---|---|---|---|
| suffix | No | Filename suffix (default: current timestamp) |
Changes observed during successful MCP inspections.
v2.0.0+make2017Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden and does disclose the critical non-destructive property (open file untouched) plus the default timestamp suffix. It omits what happens if a file with that suffix already exists and gives no hint of any return value or path/permission constraints.
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?
Three short sentences, zero filler, with the effect (copy beside the original) front-loaded ahead of the default and the usage cue. Every sentence earns its place.
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 one-optional-param, no-annotation, no-output-schema tool, the definition covers what it does, how it names output, its default, and when to use it. Only overwrite/collision behavior and return information are absent.
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 coverage is 100% and the single optional 'suffix' parameter is already documented in the schema. The description adds the filename template that consumes the suffix, but no additional format or validation semantics. Baseline 3 applies when the schema does the heavy lifting.
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?
States a specific verb and resource ('Save a copy of the model') plus the exact resulting filename pattern '<name>_<suffix>.skp'. The clause 'leaving the open file untouched' distinguishes it from the sibling 'save' without needing either schema opened.
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?
Gives a concrete scenario: 'Use this to take a backup before a risky batch of edits.' This tells the agent when to prefer it over 'save', though it never names 'save' as the alternative nor states when-not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.