omni_world_enter

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

No annotations are provided, so the description must disclose behavioral consequences. It states that the tool loads a saved world and that the name comes from a prior omni_worlds call, but it does not describe what happens to the current world, whether the operation is destructive, whether there are open-world constraints, or what happens on failure.

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?

A single sentence carries the purpose, the key parameter semantic, and the prerequisite. It is front-loaded with the primary operation and contains no wasted words.

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 the tool's simplicity — one string parameter, no output schema, and no annotations — the description covers the input and prerequisite well. However, it omits expected return behavior and side effects on the current world session. Since no annotations exist, those omissions leave an invocation- and postcondition gap.

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 input schema only says 'name' is a required string, giving the agent no semantic clue. The description compensates well by clarifying that the value is a folder name and directs the agent to obtain it from omni_worlds. For a single parameter, this is meaningfully more useful than the schema alone.

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 uses a specific verb ('Load') with a specific resource ('a saved world') and identifies the key input ('folder name'). This clearly separates it from sibling tools like omni_world_create, omni_world_scan, and omni_world_quit, which have different purposes.

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 explicitly instructs the agent to call omni_worlds first to obtain the name, which is a clear prerequisite for correct use. It does not explicitly discuss when not to use the tool or compare it to alternatives, but the practical guidance is sufficient for most invocation scenarios.

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