reinit_niagara_system

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'reinitialize' without explaining what reinitialization entails—whether it resets particle states, requires an existing Niagara component, or has irreversible effects. The agent cannot anticipate impact or side effects.

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?

The description is a single, compact sentence with no wasted words. It's easy to parse and front-loads the core purpose. However, it is under-specified, sacrificing depth for brevity, which is a slight negative against an otherwise efficient structure.

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 simple one-parameter tool with no output schema and no annotations, the description should provide more context about when to use it, what reinitialization does, and how it relates to similar tools. The current text is insufficient to guide an agent reliably, especially given the existence of reset_niagara_system as a sibling.

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?

The input schema already documents actor_name as 'Actor with Niagara component', and the description's 'on an actor' simply restates that. Schema coverage is 100%, so the description adds no extra meaning about the parameter's format or constraints, though it does reinforce the actor's role.

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 clearly states the action (reinitialize) and the resource (Niagara system) with a target actor. It is specific enough to distinguish from set_niagara_* tools, but it does not differentiate from the sibling tool 'reset_niagara_system', which could be synonymous or have a different meaning.

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 description offers no guidance on when to use this tool versus alternatives like reset_niagara_system. It does not mention prerequisites, side effects, or exclusion conditions. The implicit usage ('when you need to reinitialize a system') is tautological and not actionable.

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