Save Active Scene

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety and repeat-call profile is covered. The description restates idempotency (redundant with annotations) and adds the underlying implementation (AssetDatabase + EditorSceneManager.SaveOpenScenes), but says nothing about failure modes, e.g. what happens outside play mode or on unsaved new scenes.

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?

Three short lines, front-loaded with the action, then the trigger condition, then the repeat-call behavior. No filler or restatement of the title.

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 zero-parameter, no-output tool whose annotations already carry the safety profile, the description covers purpose, trigger and idempotency adequately. Only the absence of any note about error conditions keeps it from being fully complete.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-related gaps exist.

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?

States a specific verb and resource ('Save the active scene to disk') and even names the underlying APIs used. No sibling tool performs a save, so the agent can immediately distinguish it from the get/create/transform tools.

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?

'Use when: after create/delete/transform batches so work is not lost' gives a concrete trigger condition tied to specific sibling operations. It stops short of naming alternatives or stating when-not to call it, but no plausible alternative exists in this toolset.

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