unreal_save_all

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

Beyond the idempotentHint annotation, the description discloses that the operation writes to the project on disk, is harmless to repeat when nothing changed, and can be cancelled by the user resulting in saved=false. This adds meaningful behavioral context beyond what annotations alone provide.

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 key purpose is stated in the first sentence, followed by compact and relevant notes on behavior, arguments, return format, and usage. Every section adds value, and there is no redundant filler.

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?

The description covers purpose, persistence behavior, idempotence, parameter meaning, return payload including cancellation, failure indication, and when to use/discard. There is no missing piece needed for an agent to invoke this tool correctly.

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 description repeats the parameter meaning already present in the schema ('save_level: Also save the open level (default True)') without adding new details such as behavior when false or edge cases. Since the schema documents the single parameter adequately, no additional compensation is needed.

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 states a specific verb ('save') and resource ('every modified asset, and optionally the open level'), making its function unambiguous. It clearly distinguishes from sibling tools like list, import, spawn, and delete without any ambiguity.

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?

Explicit when-to-use and when-not-to-use guidance is provided ('Use when finishing a batch of spawns or imports...', 'Don't use when the user is still experimenting...'). It does not name a specific sibling alternative, but the contextual direction is clear and actionable.

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