new_scene

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the destructive nature of the tool through 'before clearing' and offers the save_current safeguard. However, it does not explicitly state that the current scene is cleared without recovery or what happens to unsaved changes when save_current is false.

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 two sentences: a one-line purpose and a one-line argument explanation. No filler, extraneous examples, or repetition of schema types. The main action is front-loaded, and the parameter detail is placed after, making it easy to parse.

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 tool with a single optional parameter and no output schema, this description is largely sufficient. It covers the core action and the main side-effect (clearing) with a mitigation option. A small gap is the missing explicit statement that the current scene is replaced, but the phrase 'before clearing' strongly implies it, so this is only a minor omission.

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 schema provides no parameter descriptions, so the description compensates fully. 'Save the current scene before clearing' gives clear, actionable meaning to save_current, explaining what the boolean controls and its effect on behavior. This is exactly the kind of semantic clarity an agent needs.

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: 'Create a new empty Houdini scene.' This clearly differentiates it from siblings like save_scene, load_scene, and import_file, which operate on existing or external scenes. The wording is unambiguous about what the tool does.

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?

No guidance is given on when to use this tool versus alternatives such as load_scene or import_file. The description does not mention typical use cases, prerequisites, or conditions where a different tool would be preferred. The only context is the 'before clearing' phrase, which implies a reset but is not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.