Create a new empty scene, optionally retaining current settings like units and render setup. Note: Unsaved changes will be lost.
新建空场景。可选保留当前场景的某些设置。未保存的改动会丢失。 [English] Create a new empty scene. Some session settings can be carried over. Unsaved changes are lost.
| Name | Required | Description | Default |
|---|---|---|---|
| keepScene | No | 是否保留当前场景的设置（单位、渲染参数等），默认否。 | Keep current session settings such as units and render setup, default false. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds concrete behavioral detail beyond the destructiveHint annotation by explicitly warning that unsaved changes are lost. It also explains that some session settings can be carried over, giving the agent useful insight into the tool's actual effect.
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, front-loaded with the primary action, and every sentence carries useful information. The bilingual duplication is acceptable and does not introduce noise.
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 simple single-parameter tool with no output schema, the description covers the essential action, the optional setting, and the main destructive consequence. It is complete enough for an agent to invoke correctly, though it could optionally mention what happens to the current scene beyond the data-loss warning.
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%, so the keepScene parameter is already well documented. The description only broadly mentions carrying over settings and does not add detail beyond the schema, so the baseline score of 3 is appropriate.
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 specific verb and resource: creating a new empty scene. It is clearly distinct from sibling tools like scene_open, scene_merge, and scene_reset because it emphasizes 'new empty' rather than opening, merging, or resetting an existing scene.
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 provides clear context: use this when a new empty scene is needed, and optionally carry over session settings. It implicitly communicates that existing work will be replaced via the unsaved-changes warning, though it does not explicitly name alternatives like scene_reset or scene_open.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.