ue_spawn_actor

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action (spawn) and lists parameters, but does not disclose side effects (e.g., level modification), non-idempotency, potential errors, or what the tool returns (no output schema). Minimal transparency.

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 structured with a concise purpose line followed by a clear bullet list of parameters. No redundant information; each sentence is useful. Could be slightly more compact but is well-organized.

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 5 parameters and no output schema, the description adequately covers all inputs. However, it omits return value or success feedback, and does not mention prerequisites (e.g., open level) or error conditions. Enough for basic use but leaves gaps for an agent.

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 description explains all five parameters in detail with units and examples (e.g., class_ref shows valid paths, location as [x,y,z] in cm, label used in Outliner). Schema coverage is 0% without this description, so it adds significant meaning beyond the raw schema.

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 'Spawna un attore nel livello corrente' (Spawn an actor in the current level), specifying the verb and resource. While it distinguishes spawning from other actor operations, it does not explicitly differentiate from sibling tools like ue_set_actor_transform or ue_delete_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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when-not-to-use, or contrasting scenarios with sibling tools like ue_create_blueprint or ue_list_actors.

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