niagara_add_sprite_renderer

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 that a sprite renderer is added and provides an example; it does not mention save behavior, whether an existing renderer is overwritten, whether the emitter must already be loaded, or what side effects occur. The 'emitter handle' wording also conflicts somewhat with the system_path-based parameters.

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 front-loaded, with no filler, and the KB pointer and example add some value. However, the structure is minimal for a tool with five parameters and no annotations, so the brevity is more under-specification than effective condensation.

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?

This is a mutating Niagara tool with unknown annotation semantics and five parameters, but the description does not cover emitter selection, material handling, or save behavior. The output schema exists, so return values need not be described, but the operational context is too incomplete for confident invocation.

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, but it only illustrates system_path usage in an example. emitter_id, emitter_name, material_path, and save are left completely unexplained, making it unclear how to target an emitter or configure the renderer.

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 states a specific action and target: adding a Sprite Renderer to an existing Niagara emitter, with a concrete example invocation. It is distinguishable from the sibling niagara_add_mesh_renderer by renderer type, though it does not explicitly contrast with siblings and refers to an 'emitter handle' while the parameters use system_path/emitter_id/emitter_name.

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?

No guidance is given for when to use this tool versus niagara_add_mesh_renderer, niagara_add_empty_emitter, or other Niagara tools. There is also no explanation of when to supply emitter_id versus emitter_name or whether material_path is required, leaving the agent to infer invocation context.

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