ue_create_niagara_system

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 does an above-average job by revealing that emitter stack editing is inaccessible and comparing this limitation to Blueprint graph and UMG WidgetTree constraints. It does not mention overwrite behavior or save semantics, but for a simple asset creation tool, the disclosed limitation is meaningful and adds real value beyond the schema.

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 and well-structured. It leads with the primary action, adds only essential limitation context, and lists arguments with examples. Every sentence earns its place; there is no repetition of schema information or filler content.

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?

For a simple creation tool with only two required string parameters and no output schema, the description covers the core purpose, a critical limitation, and parameter examples. It lacks details about failure cases or whether the asset is saved automatically, but these are minor gaps given the tool's simplicity and the strong contextual information already provided.

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 description coverage is 0%, so the description must compensate. It provides concrete examples for both parameters: package_path as '/Game/MyGame/VFX' and name as 'NS_Explosion'. These examples clarify expected formats and naming conventions, which is valuable given the schema only provides field names and types.

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 opens with a specific verb+resource combination: 'Crea un asset Niagara System vuoto' (Create an empty Niagara System asset). This clearly distinguishes it from sibling creation tools like ue_create_material or ue_create_blackboard, and the 'vuoto' qualifier adds precision about the asset's initial state.

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 explicitly states a key limitation: the emitter stack cannot be configured from this tool and must be built manually in the Niagara Editor. It provides practical context for when to use this tool, though it does not name alternative MCP tools for further editing (e.g., none exist). This is clear contextual guidance, but lacks an explicit 'use this when' statement.

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