ue_create_cloner

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

The description discloses that the tool creates an actor and requires a plugin. With annotations being all false, it fails to clarify important behavioral aspects such as whether the operation is idempotent, what side effects occur (e.g., instancing multiple meshes), or any required permissions. More detail is needed.

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 front-loading the core purpose and a key requirement. However, for 10 parameters, it is under-informative and could benefit from a brief parameter overview 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 tool's complexity (10 parameters, no schema descriptions, and minimal annotations), the description is insufficient. It lacks details on parameter usage, output behavior (despite an output schema existing), and fails to provide the context needed for an agent to confidently invoke the tool.

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?

With 10 parameters and 0% schema description coverage, the description provides no information about what parameters like x, y, z, label, layout, counts, spacing, or mesh_path mean. The description mentions only 'mesh' and 'layout pattern' but does not map to the schema. This severely hinders correct parameter usage.

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 verb 'Create', the specific resource 'ClonerEffector actor', and the action 'instances a mesh in a layout pattern'. It also includes a prerequisite plugin requirement, making the purpose unambiguous and distinct from sibling tools like ue_duplicate_actor.

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 mentions a required plugin, providing a necessary condition for use. However, it does not specify when to use this tool versus alternatives, nor does it give any exclusions or contexts where it should be avoided.

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