get_hlod_layer_actors

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

Annotations already cover the safety profile (readOnly/idempotent/non-destructive), yet the description adds real behavioral context beyond them: the loaded-actors-only blind spot, the world-partition-only restriction, the not_applicable/note escape hatch, and the reason (assignment would not survive a Generate).

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?

Purpose is front-loaded, the two caveats follow, and the return shape is given last. Every sentence carries information an agent needs; no filler.

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?

There is no output schema, but the description supplies the full return shape (fields, actors array, not_applicable/note) and the loading/WP caveats, so nothing needed to interpret results is missing.

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 description coverage is 100% and the single hlod_layer_path parameter is fully documented in the schema (full /Game path, matched against GetPathName()). The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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?

States a specific verb (Enumerate) and resource (LOADED actors assigned to a given UHLODLayer) and explicitly frames itself as the read-side counterpart of set_hlod_layer_actors, so an agent can distinguish it from siblings without opening a schema.

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?

Names the paired alternative (set_hlod_layer_actors) and gives concrete when-not conditions: only currently loaded actors are visible, and on a non-WP world it returns not_applicable=true instead of a list. The agent is told what conditions change the outcome.

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