add_make_struct_node

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

Annotations are absent, so the description carries the full burden. It mentions the node's behavior (takes member variables, outputs assembled struct) and gives examples, but it does not disclose side effects, prerequisites (e.g., whether the struct type must already exist), or error conditions. The reference to Ch. 13 adds context but does not reveal runtime behavior like validation or failure modes.

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 well-structured with a clear main sentence, an explanatory section, an Args list that mirrors the schema, a KB reference, and an example. It is not overly verbose and front-loads the core action. The example is appended at the end, which is acceptable given the Args list precedes it. No fluff, but the KB reference could be considered optional.

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 tool's moderate complexity (3 params, 2 required) and an output schema that likely defines the return but is not described, the description covers the essential inputs and purpose. It does not specify the return value format, but the output schema exists separately. The KB reference provides additional depth. It is reasonably complete for an agent to invoke it correctly, though it could mention expected errors or preconditions.

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 coverage is 0%, but the description explicitly defines each parameter: blueprint_name (target Blueprint), struct_type (type name with examples), node_position ([X,Y] graph position). It gives example values, which is more informative than the bare schema. It compensates for the schema's lack of descriptions, though it could specify the expected format of blueprint_name (partial path) more precisely.

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 a specific verb ('Add'), a resource ('Make [StructType] node'), and the action's purpose ('construct a struct from member values'). It distinguishes itself from sibling tools like add_break_struct_node and add_make_array_node by focusing on struct construction. The inclusion of FTransform, FVector, and custom structs provides concrete examples that differentiate it from other node-adders.

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 node takes member variables as inputs and outputs the assembled struct, which implies when it is used (to construct structs). However, it does not explicitly state when to prefer this over alternatives like add_break_struct_node or add_make_array_node, nor does it mention exclusions (e.g., only works in Blueprint graphs). The KB reference hints at broader context but does not give direct usage guidance.

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