unity_scene_save

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: requiring path for unsaved scenes, triggering a dialog if omitted, and the Save-As behavior via path. It does not mention overwriting behavior or confirmation, which is acceptable for an asset-saving operation, but additional details on side effects would improve transparency.

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 two sentences long, with the first stating the core purpose and the second adding a critical nuance. No filler or redundancy; every word earns its place. This is a model of conciseness.

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 no output schema and no annotations, the description covers the essential use cases: normal save and first-time save with path. It does not describe success feedback or error scenarios, but for a straightforward save operation, this is adequate. Missing information about overwriting or confirmation is a minor gap.

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%, so baseline is 3. The description adds meaningful context for the path parameter by explaining its mandatory use for never-saved scenes and its Save-As behavior, going beyond the schema's generic 'Asset path to save to.' The port parameter is not elaborated, but its purpose is clear from the 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 starts with a clear verb and resource: 'Save the current scene.' It immediately distinguishes this tool from siblings like unity_scene_open or unity_scene_new by focusing on saving. The additional detail about never-saved scenes requiring path or triggering a dialog further clarifies its specific role.

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 explicitly states when to use the path parameter: for a never-saved scene, and notes that omitting it for such a scene opens an interactive dialog. It does not, however, contrast this tool with alternatives (e.g., when to use Save As vs overwriting), though no direct sibling for saving exists in the list. The guidance is clear but could be more comprehensive.

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