unity_scene_new

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

With no annotations, the description discloses the destructive 'REPLACES' behavior and the refusal condition. However, it omits details like whether the old scene is recoverable (undo), return value, or any side effects beyond replacement.

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?

Two sentences, no redundancy. First sentence covers core purpose and destructive nature, second covers conditional behavior and resolution options. Every word serves a purpose.

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?

Covers the essential for a low-complexity tool: action, destructive aspect, refusal condition, and how to handle unsaved changes. Could add more about irreversibility or undo support for a destructive action.

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 description adds minimal extra value. It reiterates the purpose of saveFirst and discardUnsavedChanges from the refusal context, but does not enrich port parameter meaning.

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?

Clearly states 'Create a new empty scene (REPLACES the current one)', specifying the verb, resource, and the key behavioral distinction of replacement. Distinguishes from sibling tools like unity_scene_open and unity_scene_save.

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?

Gives explicit context for when the tool refuses (unsaved changes) and how to proceed (saveFirst or discardUnsavedChanges). Does not explicitly mention alternatives but implies using saveFirst requires prior save tool usage.

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