ue_open_level

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

No annotations are provided, so the description must convey behavioral traits. It only states it opens an existing level, without disclosing side effects like closing the current level, handling unsaved changes, or requiring the level to exist. The description is insufficient for a tool with no annotations.

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 very short, consisting of one line plus a parameter example. It is front-loaded with the action but lacks structure (no title, no sections). While concise, it is under-specified for a useful tool description.

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 annotations or output schema, the description should be more thorough. It omits details about return values, error handling, and behavioral nuances (e.g., does it reload the level?). The minimal information is inadequate for a tool in a complex environment like UE.

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 adds a docstring with a concrete example for the 'path' parameter ('/Game/MyGame/Levels/L_Main'), which provides meaningful guidance beyond the schema's type and title. With 0% schema coverage, this compensates well.

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 it opens an existing level in the editor (verb+resource). The sibling tools include ue_new_level, which creates a new level, distinguishing the purpose. However, it does not explicitly differentiate from other 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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like ue_new_level or ue_spawn_actor, nor does it mention prerequisites or conditions.

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