new_scene

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

With no annotations provided, the description carries the full burden and does so well. It discloses key behavioral traits: it clears the current scene, creates a new empty one, and explains the 'force' parameter's impact on saving changes. It also mentions the return structure (success and message), though no output schema exists. No contradictions with annotations.

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 well-structured and appropriately sized, with a clear purpose statement, parameter details, return information, and examples. Every sentence adds value, though it could be slightly more concise by integrating the examples more tightly. It is front-loaded with the core functionality.

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?

Given the tool's complexity (a destructive operation with one parameter) and lack of annotations and output schema, the description is quite complete. It covers purpose, behavior, parameters, and returns. However, it could benefit from mentioning potential errors or edge cases, such as what happens if saving fails in non-force mode.

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%, so the description must compensate fully. It does so by thoroughly explaining the single parameter 'force': its purpose (whether to force creation without saving), default value ('true'), and the effect of both 'true' and 'false' values. This adds significant 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 clearly states the specific action ('新建/重置场景' - create/reset scene) and resource ('在 3ds Max 中' - in 3ds Max), distinguishing it from siblings like 'open_scene' or 'save_scene'. It explicitly mentions clearing the current scene and creating a new empty one, providing precise functionality.

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 description provides clear context on when to use this tool (to start fresh or reset a scene) and includes examples for different scenarios (force vs. non-force). However, it does not explicitly state when NOT to use it or compare it to alternatives like 'open_scene' for loading existing files.

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