Find Unreal Engine level actors by name pattern, with wildcard support. Retrieve matching actors to inspect or manage them in editor workflows.
Find actors in the level by name pattern (supports wildcards).
KB: see knowledge_base/10_WORLD_BUILDING.md#overview Example: find_actors_by_name(pattern="Example")
| Name | Required | Description | Default |
|---|---|---|---|
| pattern | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions wildcard support and a KB reference, but doesn't disclose whether the search is case-sensitive, whether it returns partial matches, what the output format is, or any side effects. For a read-only search tool, the lack of behavioral detail is a gap.
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 short and front-loaded with the core purpose. The KB reference and example are useful, though the example adds limited value beyond the schema. 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?
With no annotations, no output schema details, and 0% schema coverage, the description is incomplete. An agent needs to know wildcard syntax, match semantics, and what the result looks like. The KB reference helps but is not self-contained.
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%, so the description must compensate. It explains that 'pattern' is a name pattern with wildcard support and gives an example, but doesn't specify wildcard syntax (e.g., '*' vs '%'), case sensitivity, or whether the pattern matches actor labels or class names. The example is minimal.
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 a specific verb ('Find') and resource ('actors in the level') with a name pattern supporting wildcards. It is distinguishable from sibling find_actors_by_class, though it doesn't explicitly name that sibling.
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 implies usage context: searching actors by name pattern with wildcard support. It provides an example call. However, it doesn't explicitly state when to prefer this over find_actors_by_class or get_actors_in_level, nor any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.