Creates a new empty Houdini scene, with an option to save the current scene first, so you can start fresh without losing work.
Create a new empty Houdini scene.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "new_scene"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| save_current | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does not state that creating a new scene discards the currently open scene, nor how the save_current parameter guards against data loss — arguably the single most important behavior for this tool.
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?
A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the cause of the disclosure gaps noted elsewhere.
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 scene-replacing mutation with no annotations, no output schema, and an undocumented boolean parameter, so the description should do far more. As written, an agent cannot know whether unsaved work is lost or what save_current does.
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 description coverage is 0% and the description never mentions save_current. The parameter's purpose (presumably saving the current scene before replacing it) is left entirely implicit, so the description adds no meaning beyond the bare schema.
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 gives a specific verb and resource ("Create a new empty Houdini scene"), which is unambiguous and distinguishable from siblings like load_scene or get_scene_info. It stops short of explicitly differentiating itself from those siblings, so it does not reach the top score.
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 on when to use this versus alternatives such as load_scene, nor any prerequisite or warning context. The agent must infer usage entirely from the name and one-line purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.