spawn_blueprint_actor

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the spawning action but does not mention possible failure modes, whether an existing actor with the same name is affected, persistence of the spawned actor, or any level state changes. This leaves important behavioral traits undisclosed.

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 compact and well organized: a one-line summary, a clear Args block, a KB pointer, and a practical example. Every section earns its place, and the most important information is front-loaded. The formatting is slightly mechanical but not wasteful.

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 output schema exists and parameters are well documented, the description is adequate for calling the tool. However, it omits sibling differentiation and behavioral expectations, which are relevant in a toolset with 'spawn_actor' and many blueprint-node spawning tools. It is a minimum-viable description rather than a fully contextual one.

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 0% schema description coverage, the description must compensate, and it does: each of the four parameters is given meaningful semantics ('Name of the Blueprint asset', 'Name to give the spawned actor', '[X, Y, Z] world location', '[Pitch, Yaw, Roll] in degrees'). The example also clarifies the asset-path format. It adds clear value over the bare 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 a specific action and resource: 'Spawn an actor in the level from a Blueprint class.' This is a precise verb+object pairing. However, it does not explicitly contrast itself with the similarly named sibling 'spawn_actor', so it slightly misses an opportunity for differentiation.

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 an example invocation and parameter list, which explains how to call the tool, but it gives no guidance on when this tool should be chosen over alternatives like 'spawn_actor' or 'add_spawn_actor_node'. There are no exclusions, prerequisites, or context for selection among the many sibling tools.

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