set_niagara_system_deterministic

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=true, so the safety profile is partly covered. The description adds genuinely new behavioral context beyond that: the write goes through reflection, and the call reports old/new values plus applied and saved flags, which tells the agent the mutation can fail to apply or persist. It does not explain why the operation carries a destructive hint or whether it auto-saves the package.

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 sentences, front-loaded with the action and followed by the return contract; nothing is padded. The Returns block is slightly boilerplate in style, but given the absence of an output schema it is information-bearing rather than 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 two-parameter mutation tool with full schema coverage and annotations, the description is close to complete: it names the mechanism and documents the return payload even though no output schema exists. The remaining gap is the missing routing against the sibling set_niagara_system_properties and any persistence/prerequisite note.

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 system_path and deterministic already carry their own descriptions. The description links the boolean parameter to the concrete bDeterminism property, but adds no format, default, or constraint detail beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: it sets the bDeterminism UPROPERTY on a Niagara system. That is precise enough for an agent to know exactly what is mutated. However, it does not distinguish itself from the existing sibling set_niagara_system_properties, which could plausibly also write system-level properties.

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?

There is no when-to-use, when-not-to-use, or alternative tool guidance. The description never mentions set_niagara_system_properties, which is the obvious ambiguity for an agent choosing between the two. Usage must be inferred entirely from the name.

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