scene-save

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects such as overwriting existing files, potential failures (e.g., missing scene), authentication requirements, or whether the operation is reversible. The phrase 'save to the existed scene asset file' hints at overwriting but is not explicit.

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 concise with two sentences, no unnecessary words. It is front-loaded with the core action, then provides a pointer to a related tool. Every sentence earns its place.

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 simplicity (save an opened scene), no output schema, and complete parameter descriptions, the description covers most essential aspects. However, it lacks information about error conditions or what happens if the save fails, which would enhance completeness.

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%, baseline is 3. The description adds value by explaining that empty 'openedSceneName' saves the current active scene and that null/empty 'path' saves to the existing asset file. This supplements the schema descriptions with practical usage details.

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 action: 'Save Opened scene to the asset file.' It uses a specific verb-resource pair and distinguishes itself from other scene tools like scene-open or scene-create by focusing on saving. References a related tool (scene-list-opened) for context.

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 by mentioning the prerequisite 'scene-list-opened' tool for obtaining scene names. It implies when to use the tool (after opening a scene), but does not explicitly state when not to use it or compare to alternatives.

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