scene_save_as

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds the non-obvious behavior that missing folders are automatically created. However, it does not mention that saving may overwrite an existing file or that the new path becomes the current scene path by default, though keepPath is documented in the schema.

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 compact: two short bilingual sentences. The primary action is front-loaded, and the folder-creation behavior is stated as a concise parenthetical and then repeated in English. No filler or irrelevant context is present.

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 file-writing tool, the description covers the core action and folder creation, but it does not explicitly warn about overwriting existing files or contrast with scene_save. The destructiveHint annotation partially compensates, but the manual remains slightly incomplete for safe autonomous use.

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 100%, and both path and keepPath already have clear descriptions in the input schema. The tool description does not add additional parameter-level meaning beyond the schema, so the baseline score of 3 applies.

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 a specific action and resource: '把当前场景另存到指定路径' / 'Save the current scene to a given path'. It also adds a useful detail about creating missing folders. This distinguishes it from scene_save, which implies saving without a new path.

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 provided about when to use this tool instead of scene_save, scene_open, or scene_merge. There are no alternatives or exclusions mentioned, so the agent must infer usage from the name and description.

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