new_scene

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

With no annotations, the description carries the full burden. It usefully discloses the key destructive trait — the current scene is 'cleared' and the save_current flag preserves it beforehand — but does not say whether the clear is undoable, what happens to unsaved work when save_current is false, or any permission/cost considerations.

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?

Very short and front-loaded with the core action; the Args block is the only slightly awkward element, but there is no wasted prose.

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 scene-reset tool with no annotations and no output schema, the description covers the essential action and the save flag but is thin on consequences (data loss, reversibility) that an agent should weigh before invoking.

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 0%, so the description must compensate, and it does: it explains that save_current means 'Save the current scene before clearing,' giving the boolean real meaning beyond the bare 'boolean, default false' in the 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?

States a specific verb and resource ('Create a new empty Houdini scene'), which is unambiguous. It distinguishes itself by implication from load_scene (loading an existing file), but never explicitly names a sibling, so it stops short of a 5.

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 phrase 'empty scene' and 'before clearing' imply the use case (start fresh / reset the workspace), but there is no explicit when-to-use or when-not-to-use guidance relative to load_scene or save_scene. Usage is inferable rather than stated.

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