ue_list_actors

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

No annotations provided, and the description does not state whether the tool is read-only, destructive, or safe. It merely describes the action without behavioral traits. Since it is a list operation, likely safe, but not disclosed.

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 a single concise sentence. It is front-loaded and contains no fluff, but could benefit from additional details without becoming verbose.

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?

Given the simple tool with two optional params and an output schema, the description is adequate but lacks completeness: no mention of expected output format (though output schema exists), no error handling, and no mention of case sensitivity or wildcard behavior.

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 coverage is 0%, yet the description only vaguely mentions filters on name and class. It does not explain that parameters are substring matches (name_contains, class_contains) or any constraints like case sensitivity. The description adds minimal value beyond the parameter names.

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 lists actors of the current level, distinguishing it from sibling tools like ue_spawn_actor (create) and ue_delete_actor (delete). It is specific but lacks detail on scope beyond current level.

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 vs. alternatives (e.g., ue_list_assets for assets). No exclusions or prerequisites mentioned. The context signal shows many siblings, but the description does not help choose.

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