get_niagara_module_input_binding

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

No annotations are provided, so the description carries the full burden. It details internal implementation (using specific Unreal Engine functions and replicating non-exported logic) and discloses key behaviors like recursive descent for dynamic inputs. This is highly transparent.

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 moderately long but well-structured: a concise summary, then output details, then internal notes, then parameter list. A few more words than strictly necessary, but every part adds value. Front-loading the answer question helps.

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 complexity (6 params, 4 required) and no output schema provided, the description fully covers what the tool does, what it returns (with field details), and the meaning of all parameters. No critical gaps remain.

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?

With 0% schema_description_coverage, the description compensates fully. Every parameter is explained in the 'Args' section with clear semantics (e.g., system_path: Niagara System asset, max_depth: default 3). This adds significant value beyond the raw schema.

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 resolves the actual binding of each module input, distinguishing it from siblings like get_niagara_module_inputs and get_niagara_rapid_iteration_parameters. It lists specific output fields (mode, value, linked_parameter, etc.), making the purpose very specific.

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 explains that this tool answers a question that sibling tools cannot, providing explicit context for when it should be used. However, it does not explicitly state when not to use it or mention alternatives beyond the two named siblings.

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