Clear the current 3D workspace scene to start a fresh model. Call once at the beginning to remove all existing objects and avoid conflicts.
Mulai adegan KOSONG. Menghapus isi adegan ruang kerja ini — panggil sekali di awal sebuah model, bukan di tiap langkah.
| Name | Required | Description | Default |
|---|---|---|---|
| ruang | No | Nama ruang kerja; tiap ruang punya adegan.blend sendiri. | utama |
| satuan | No | METRIC |
Changes observed during successful MCP inspections.
v1.6.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark destructiveHint=true, and the description adds specifics about what is destroyed ('Menghapus isi adegan ruang kerja ini') and the recommended single-call cadence. No contradiction with annotations exists; it enriches them by naming the affected scope.
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 compact: one clause naming the purpose/effect, one clarifying destructive scope, and one usage directive. No filler or redundant restatement of the tool name.
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 destructive initialization tool with no output schema, the description covers purpose, scope, and invocation timing. The main missing piece is the meaning of the satuan parameter; otherwise an agent has enough context to call it correctly.
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 only 50% and the description adds no parameter meaning. The 'ruang' parameter has a schema description, but 'satuan' is undocumented in both the schema and description, and the prose does not explain how unit selection affects the new empty scene.
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 action: 'Mulai adegan KOSONG' and 'Menghapus isi adegan ruang kerja ini,' so an agent can tell it initializes/clears the current workspace scene. It does not explicitly name or contrast sibling tools, but the EMPTY-scene framing separates it from view, load, export, and other scene-related tools.
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?
It gives clear when-to-use guidance: 'panggil sekali di awal sebuah model, bukan di tiap langkah' (call once at the start of a model, not at every step). This is positive and negative usage direction, though it does not mention alternatives by name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.