niagara_add_mesh_renderer

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

There are no annotations, so the description carries the full behavioral burden. It discloses that the operation adds a renderer to an existing emitter, but it does not describe the asset mutation, the save default (true), whether existing renderers are replaced, or failure conditions. This is significant for a mutating tool.

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 short and front-loaded with the action, and the example adds concrete invocation details without fluff. The KB pointer is a small addition, but the overall structure is efficient.

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 6-parameter tool with no annotations and zero schema description coverage, the description is incomplete: it leaves emitter targeting, optional parameters, and save behavior unexplained. The output schema exists, so return values do not need to be covered, but the invocation contract is still under-specified.

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 explain parameters, but it only provides a minimal two-parameter example. It does not explain emitter_id vs emitter_name selection, the optional material_path, or the side effect of save. The property names are somewhat self-explanatory, but the critical target-selection semantics are missing.

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 uses a specific verb and resource: 'Add a Mesh Renderer' to an 'existing Niagara emitter handle', which distinguishes it from the sibling niagara_add_sprite_renderer. However, the term 'emitter handle' is undefined and the description does not clearly explain that emitter_id/emitter_name select the target emitter, so it is not a 5.

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 explicit when-to-use or when-not-to-use guidance is provided, and no alternatives such as niagara_add_sprite_renderer or niagara_add_empty_emitter are mentioned. The only usage signal is the implied condition that an existing emitter must be present, which is not enough for an agent to choose this over sibling tools.

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