ue_actor_hierarchy

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool returns a hierarchy, but does not mention if it is read-only, recursive, how the tree is structured, or any side effects. This is insufficient for a tool with no annotational safety hints.

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 concise with two sentences covering purpose and parameter guidance. No redundant information. However, it is in Italian, which may be less accessible for English-centric agents, slightly reducing effectiveness.

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 tool is simple with one optional parameter and an output schema exists, so the description need not detail return values. However, it omits behavioral context (e.g., whether the tree includes all actors or only spawned ones, depth limit). Adequate but could be more complete.

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 single parameter 'label' is described as 'se indicato, parte da quell'attore invece che dalle radici' (if provided, starts from that actor instead of roots). This adds clear meaning beyond the schema, which only defines type and default. Schema description coverage is 0%, so the description 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 states 'Albero padre/figli degli attori del livello' (parent/child tree of level actors), which clearly indicates the tool retrieves the actor hierarchy. It distinguishes from sibling tools like ue_list_actors (flat list) and ue_spawn_actor, but lacks an explicit verb like 'get' or 'list', slightly reducing clarity.

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 explains the label parameter for specifying a start actor, but provides no guidance on when to use this tool versus alternatives (e.g., ue_list_actors). No explicit when-to-use or when-not-to-use context is given.

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