world_info

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

With no annotations, the description carries full burden for behavioral transparency. It does not indicate whether the tool is read-only, what side effects it has, or whether it returns current state or modifies anything. The bare list of items gives no clue about behavior.

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 extremely short and free of fluff, but it is so terse that it sacrifices clarity. It fits in one sentence but fails to convey meaningful information about the tool's function.

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 lists game-related entities but does not explain what the tool does with them—whether it retrieves, modifies, or reports their status. It lacks context about return format or purpose, making it incomplete for an agent deciding to call it.

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, so there are no parameter semantics to describe. The baseline of 4 applies because the absence of parameters is clear and no description 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 is a noun phrase listing game objects (world, player controller, pawn, game instance, game mode) but does not state what the tool does with them. It lacks a verb like 'get' or 'list', making the purpose ambiguous compared to sibling tools like inspect_object or get_property.

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 guidance is provided on when to use this tool versus alternatives such as dump, get_property, or inspect_object. The description does not explain scenarios where world_info is preferred.

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