niagara_add_empty_emitter

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Add' and gives an example; it does not mention whether the target system must already exist, whether existing asset data is modified, how the save parameter affects persistence, or what side effects the 'add_default_modules=false' default may have. The KB link is not embedded context.

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, front-loads the core action, and includes a concrete usage example plus a KB pointer. It stays short and readable, though some of that brevity comes at the expense of parameter and behavioral context.

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 mutating tool with no annotations and four parameters, the description omits prerequisites, side-effect details, and the meaning of the optional parameters. An output schema exists, so return values need less explanation, but the missing operational context makes the description incomplete.

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%, and the description only demonstrates system_path via an example. It adds no meaning for save, emitter_name, or add_default_modules beyond their names and defaults, which is insufficient compensation for a schema with no parameter documentation.

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 ('Add') and target resource ('Niagara System asset'), and the phrase 'native empty emitter handle' conveys specific scope. It does not explicitly differentiate from sibling tools like niagara_create_system, but the verb+resource combination is clear enough that an agent can tell it is an additive emitter operation.

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 call but no guidance on when to use this tool versus alternatives such as niagara_add_sprite_renderer, niagara_add_mesh_renderer, or niagara_create_system. The KB reference is a pointer to external docs, not an explanation of selection conditions.

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