set_niagara_component_matrix

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

Adds substantial context beyond the annotations: it explains the internal mechanism (SetVariableMatrix), discloses that GetNiagaraVariableMatrix is not public so round-trip readback is unavailable, and defines what verified:true actually means. This is exactly the kind of limitation disclosure annotations cannot carry, and nothing contradicts the destructive/idempotent hints.

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?

Front-loads the action in the first sentence, then layers mechanism/limitation, then the return shape. Every sentence earns its place with no filler.

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 no output schema, the description supplies both the behavioral caveat and the full return shape, so an agent knows what it gets back and how to interpret 'verified'. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the schema already documents all three parameters including the 4x4 row-major matrix ordering. The description repeats that ordering rather than adding new meaning, so 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?

States a specific verb and resource ('Sets a Matrix (FMatrix) override parameter on a spawned Niagara component') and identifies the matrix variant of the set_niagara_component_* family. An agent can distinguish it from set_niagara_component_vec4/quat siblings without opening a 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?

The phrase 'on a spawned Niagara component' implies the component must already exist, but there is no explicit when-to-use, prerequisite, or alternative guidance (e.g., versus the other set_niagara_component_* matrix-adjacent setters or get_niagara_component_matrix).

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