get_niagara_emitter_data_interfaces

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds value: it names the underlying array read and enumerates the binding fields returned. It also clarifies that this command cannot mutate bindings, heading off a wrong call. It does not discuss pagination or performance, but for this data size that is minor.

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?

Purpose is front-loaded in the first sentence, followed by implementation context and a Returns line. Most content earns its place, though the raw C++ type names (FVersionedNiagaraEmitterData::EmitterDependencies, TArray<FNiagaraDataInterfaceEmitterBinding>) are heavier than most callers need.

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 read-only list tool with full annotation coverage and complete parameter docs, the description is nearly self-sufficient: it explains the read target, the immutability boundary, and the return shape even though no output schema exists. The only blemish is a slight mismatch between the field list in the body (name, type, interface_class, interface_path, instance_index) and the Returns block (emitter_name, binding_mode).

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?

With schema description coverage at 100% and only two parameters, the schema already defines system_path (asset path of the Niagara System) and emitter_name (name of the emitter handle). The description adds no further constraint, format, or lookup guidance for either parameter, so the baseline 3 applies.

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 opening sentence gives a specific verb+resource+scope: list data interface bindings on a Niagara emitter, and the '(read-only)' tag pins down the operation class. The added detail about reading FVersionedNiagaraEmitterData::EmitterDependencies makes the target unambiguous. It stops short of naming a sibling (e.g. get_niagara_data_interfaces) to contrast against, so an agent must infer the boundary.

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?

It signals the read-only contract and notes that adding/removing bindings requires view-models and is editor-only, which is a useful 'when not' hint. However, it never states when to pick this over look-alike siblings such as get_niagara_data_interfaces or get_niagara_data_interface_info. Usage is implied rather than routed.

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