get_niagara_component_matrix

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it explains the value is read from the component's OverrideParameters store rather than a getter (no GetNiagaraVariableMatrix exists) and that a missing override returns found:false with an empty matrix, never a faked identity — an important edge-case disclosure.

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 core action, then the implementation rationale, then the not-found contract and return shape. Dense but well structured; the engine-internal detail is somewhat verbose, though it directly supports behavioral transparency.

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 helpfully supplies the return shape and the found:false edge case, plus the set/get pairing. Complete for a two-parameter read tool, though it omits any note on which other readers to use for non-matrix variable types.

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 both parameters are already documented there, and the description adds only marginal meaning (that the looked-up variable is a Matrix4/FMatrix44f type). This matches the baseline-3 case where the schema does the heavy lifting.

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 ('Reads a Matrix (FMatrix4f) override parameter back off a spawned Niagara component') and names the exact counterpart tool it round-trips with, set_niagara_component_matrix. An agent can distinguish it from the many other get_niagara_* and set_niagara_component_* 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?

Frames the tool as the round-trip reader for set_niagara_component_matrix, which gives clear retrieval context. It does not state explicit exclusions (e.g. what to use for non-matrix variable types such as get_niagara_user_parameter), so it stops short of full when/when-not guidance.

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