set_niagara_component_quat

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

Annotations already declare the mutation profile (readOnly false, idempotent, destructive), so the bar is lower, yet the description adds real value: it explains that it resolves the UNiagaraComponent on the owner actor, calls SetVariableQuat, then reads back via GetNiagaraVariableQuat, and that the override is added locally if needed. The write-then-verify behavior is genuinely non-obvious 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?

Two front-loaded sentences covering action, mechanism, and return shape, with no filler. The return breakdown is dense but justified because there is no output schema; sizing is appropriate.

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 destructive mutation tool with no output schema, the definition supplies the mechanism, the read-back verification semantics, and the explicit return shape. It lacks only guidance on failure/permission conditions and alternatives, which keeps it short of a 5.

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 w/x/y/z, actor_name and variable_name are already documented in the schema, and the baseline is 3. The description's mention of the (W, X, Y, Z) serialization order marginally reinforces the schema's per-component descriptions but adds little param meaning beyond it.

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?

States a specific verb (Sets), specific resource (a Quat/FQuat override parameter on a spawned Niagara component), and even the underlying API calls. Against a large family of sibling set_niagara_component_* tools, the name plus description unambiguously identify the quaternion variant.

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?

Usage is only implied: an agent can infer this is the tool for quaternion variables when the other set_niagara_component_* tools handle floats, vectors, colors, etc., but the description never states when to choose it over set_niagara_component_vec4 or set_niagara_component_vector, nor any prerequisites (e.g. that the component must already be spawned).

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