ue_editor_close

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

With no annotations, the description carries full burden. It discloses the two-phase approach (clean close attempt then process termination) and the effect of each parameter. However, it does not mention what happens if save_all=False and clean close fails (still terminates), which is somewhat ambiguous.

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 concise with two short paragraphs. The purpose is stated first, followed by a clear explanation of the two-step process and parameter descriptions. No redundant information.

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, the description covers the essential behavior (close modes, parameter effects). It could mention return value or prerequisites (editor must be open), but these are implied. Complete enough for a close tool.

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 0%, so the description must explain parameters. It does so effectively: save_all saves level/assets before closing, force skips clean close and terminates directly. This adds meaning beyond the schema's boolean names.

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 closes the editor, specifying a two-step process (clean close then force terminate). It distinguishes from sibling tools like ue_editor_open (open) and ue_save_all (save).

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 explains when to use force (if clean close fails or force=True), but does not explicitly mention when not to use this tool or suggest alternatives (e.g., use ue_save_all for saving only). The usage context is implied rather than explicit.

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