unity_scene_save

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

No annotations are provided, so the description must carry the full burden. 'Save' implies a write operation, but the description does not disclose if it overwrites the file, creates a backup, or requires the scene to be already saved. It is not contradictory to any annotations since none exist.

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 extremely concise (one sentence, 5 words) and is front-loaded with the key action. However, it might be too terse, missing context that could be included without significant bloat.

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 simplicity of the tool (single parameter, no output schema), the description is minimally adequate. However, it lacks any mention of what happens after saving (e.g., file path, overwrite behavior) which could be important for an agent.

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% (1 parameter, 'port', with a description). The description does not add additional meaning beyond the schema's parameter description, so a baseline score of 3 is appropriate.

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 'Save the current scene' clearly states the verb ('Save') and resource ('current scene'). It is distinct from sibling tools like unity_scene_new, unity_scene_open, or unity_scene_info, but does not explicitly differentiate itself from them.

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 does not provide explicit guidance on when to use this tool versus alternatives. The input schema mentions that the 'port' parameter is important for parallel-safe routing, implying a specific context (multiple instances), but no direct comparison to sibling tools like unity_scene_info or unity_build.

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