get_niagara_rapid_iteration_parameters

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

No annotations provided, so description carries full burden. It states the tool returns parameter names, types, current values, and module ownership. It does not explicitly state it is read-only, but the name 'get' implies that. No mention of side effects, auth needs, or rate limits.

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 concise with clear structure: a brief purpose statement followed by bulleted parameter descriptions. It is front-loaded and easy to parse, though could be slightly more streamlined.

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?

Given the presence of an output schema (not shown), the description adequately explains input parameters and return values. It is sufficiently complete for an agent to understand the tool's function, though it lacks warnings about sibling tools.

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 Args section describes each parameter in detail, including system_path, emitter_name, script_usage, and filter. It provides examples for filter (e.g., 'Color', 'SpawnRate'), adding significant meaning beyond the schema which only has names and types. Schema description coverage is 0%, but the description fully compensates.

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 tool retrieves rapid iteration parameters (actual configurable values on modules) and lists examples like spawn rate, gravity, colors, etc. This distinguishes it from sibling getter tools that retrieve system info or emitters.

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?

No guidance on when to use this tool versus alternatives such as get_niagara_module_inputs or set_niagara_rapid_iteration_parameter. The description does not mention prerequisites or context for usage.

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