ue_save_all

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

No annotations are provided, so the description must carry the full behavioral burden. It states the core action (saving) and its scope (all modified assets and levels), but it does not disclose potential side effects such as overwrite behavior, whether unmodified assets are ignored, or if it blocks. This is adequate but minimal.

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 only two sentences, with the primary action front-loaded. The Ctrl+Shift+S reference is a helpful, concise addition. Every word earns its place.

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 save-all tool with no parameters, no output schema, and no nested objects, the description completely covers the tool's purpose and behavior. The equivalence to a well-known editor shortcut provides additional context.

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 schema coverage is effectively 100%. The description does not need to explain parameters, and the baseline for no-parameter tools is 4. Nothing is missing here.

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 clearly states the tool's function: 'Save all modified assets and levels.' This is a specific verb+resource combination that distinguishes it from siblings like ue_save_level, which focuses only on the current level.

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 gives clear context on when to use the tool via the Ctrl+Shift+S equivalence, which is a well-known save-all shortcut. It implicitly contrasts with ue_save_level by emphasizing 'all,' but it does not explicitly mention alternatives or exclusions.

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