scene_save

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

The annotation declares readOnlyHint=true, but the description says the tool 'saves' the current scene, which is a write/persisting operation and contradicts the read-only hint. The description does not clarify this conflict or disclose side effects such as overwriting the existing file.

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 and front-loaded with the key verb and resource. However, it repeats the same content in Chinese and English, so the bilingual duplication adds length without adding new information.

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 simple, zero-parameter save operation, the description covers the essential behavior and the never-saved edge case. It does not specify return values or success/failure behavior, but those are not critical for a save tool; the contradictory readOnlyHint annotation prevents a perfect score.

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?

The tool has zero parameters and the schema description coverage is 100%, so there is no parameter meaning for the description to add. The baseline of 4 for zero-parameter tools 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 uses a specific verb and resource: 'Save the current scene.' It also distinguishes itself from sibling scene_save_as by noting that if the scene has never been saved, it behaves like save-as.

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 clearly says when to use it: whenever the current scene should be saved. It also covers the edge case where the scene has never been saved, making the behavior predictable, though it does not explicitly name scene_save_as as the alternative for forcing a new save location.

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