set_niagara_emitter_allocation_mode

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the return shape includes applied/saved/save_error, revealing that the operation auto-persists the asset and can report a save failure, and it flags PreAllocationCount as conditionally meaningful.

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?

Two tight sentences, purpose front-loaded, and no output schema exists, so the explicit Returns block earns its place by telling the agent what the call yields. Zero wasted text.

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 mutation tool with full annotation coverage and a fully documented schema, this is nearly complete: it names the target property, the conditional parameter, and the return shape. It stops short of explaining the destructive consequences or the version-specific nature implied by 'FVersionedNiagaraEmitterData', so it is not flawless.

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 100%, so the schema already documents all four parameters including accepted enum values for allocation_mode. The description only restates the core property names (EParticleAllocationMode, PreAllocationCount), adding marginal meaning beyond the schema, so the baseline 3 is appropriate.

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 names a specific verb (Set) and resource (EParticleAllocationMode on a Niagara emitter's FVersionedNiagaraEmitterData), which is precise enough to distinguish it from other Niagara setter siblings like set_niagara_emitter_enabled or set_niagara_emitter_sim_target. It doesn't explicitly contrast with alternatives, but the specificity of the target property makes the purpose unambiguous.

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 states what the tool does but gives no when-to-use guidance, no prerequisites (e.g., the system/emitter must already exist), and no indication of when this mutation is appropriate versus other emitter settings. Nothing routes the agent among the many sibling emitters tools.

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