add_spawn_niagara_at_location_node

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

No annotations are present, so the description carries the full burden. It discloses the action (adds a node) and return shape (node_id and success flag), but does not mention side effects such as whether the Blueprint is compiled, whether existing graph contents are affected, or validations on the Niagara asset path. Adequate but with clear gaps.

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?

Front-loaded purpose, tight sections for Args/Returns/KB/Example, and no filler. The example adds actionable value without bloating the description.

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?

Covers action, args, return, and example; the output schema handles return detail. The main gap is the failure to disambiguate from add_spawn_emitter_at_location_node and note whether niagara_system_path can be empty, but overall it is sufficient for a node-creation 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 0% schema coverage, the description compensates by explaining all four parameters, including the default graph name, asset path format with an example, and optional node position. It does not explicitly mark niagara_system_path as required despite its essential role, and relies on the schema for requiredness.

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?

States a specific verb and resource: "Add a 'Spawn System At Location' node for a Niagara particle system." It also gives concrete use cases like spawning explosion VFX. It does not explicitly distinguish this from sibling add_spawn_emitter_at_location_node, so it misses the strongest 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?

Includes explicit usage intent: "Use this to fire a one-shot Niagara VFX effect at a world location from within a Blueprint graph" with examples. No exclusions or alternative routing are provided, so it does not reach the top tier.

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