ue_actor_hierarchy

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

No annotations provided, so full burden on description. It states the output is a tree structure but does not disclose if it's a read operation, error behavior (e.g., invalid label), or side effects (e.g., potential performance for large hierarchies). Lacks safety and mutation context.

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?

Two sentences: first defines the core purpose, second explains the optional parameter. No wasted words, front-loaded, easy to parse. Adequately sized for a simple tool.

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?

For a simple tool with one optional parameter and existing output schema, the description covers the basic functionality. However, it misses behavioral context (safety, prerequisites) and edge cases. Without annotations, an agent might not know if the tool is safe or requires specific state.

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 0%, but the description compensates well by explaining the 'label' parameter: starts from that actor instead of roots. This adds meaningful context beyond the schema's bare type 'string or null'. However, no further details (e.g., format, case sensitivity) are given, though the param is simple.

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 returns a parent/child tree (hierarchy) of level actors. The verb 'albero padre/figli' is specific and resource-oriented. It distinguishes from the flat list tool 'ue_list_actors' among siblings.

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 on when to use this tool versus alternatives like ue_list_actors or ue_spawn_actor. It does not mention prerequisites (e.g., level must be open) or exclude cases (e.g., no actors). The description only implies use for hierarchy viewing.

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