set_niagara_component_vector

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=false), so the bar is lower. The description still adds real value by explaining the mechanism: it resolves the UNiagaraComponent on the owner actor, calls SetVariableVec3, and reads the value back to verify. That read-back/verification behavior is not derivable from the annotations or schema.

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?

Three compact sentences: purpose first, mechanism second, return shape third. Every sentence carries information and nothing is padded.

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?

With no output schema, the description correctly documents the return object inline, and annotations cover the mutation/safety profile. The only minor gap is that it does not state what happens when the component cannot be resolved on the owner actor, though the 'Resolves the UNiagaraComponent' phrasing implies that step can fail.

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 three parameters (actor_name, variable_name, vector) are already fully documented in the schema. The description's mention of 'override parameter' and 'owner actor' maps loosely to those fields but adds no format or constraint detail beyond what the schema provides; 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 description opens with a specific verb+resource: 'Sets a Vector3 override parameter on a spawned Niagara component.' The type qualifier (Vector3) cleanly separates it from the many sibling setters such as set_niagara_component_float, set_niagara_component_position, and set_niagara_component_color, so an agent can route without opening any schema.

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 context is only implied: the tool works on a 'spawned Niagara component' resolved on the owner actor, which hints that the component must already exist. There is no explicit when-to-use versus alternatives (e.g., set_niagara_user_parameter or the module-input setters) and no stated preconditions or failure behavior.

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