add_spline_mesh_component

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

With no annotations, the description bears full responsibility for behavioral disclosure. It hints at how the component deforms a mesh but does not disclose side effects (persistent blueprint modification, need to save/compile), preconditions (valid blueprint, valid mesh path), or how start/end positions are actually applied (whether the tool wires SetStartAndEnd itself).

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 purpose is front-loaded, followed by a compact args list, a KB reference, and a concrete example. The 'From Ch. 19' aside is mild noise, but overall the structure is readable and every major section earns its place.

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?

The description includes enough to make a basic call (example, args, KB link), but it leaves ambiguity about whether the tool automatically wires SetStartAndEnd in the Construction Script or expects the user to do it. It also doesn't mention validations, coordinate system, or what happens with the default empty static_mesh_path. For a 5-parameter mutation tool with no annotations, more is needed.

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 0%, so the description must compensate. It provides one-line meanings for all five parameters, e.g., 'Static Mesh asset to deform' and 'Start point world position', adding clarity beyond raw names. However, 'Component name: Component name' is tautological, and coordinate space/format details are left implicit.

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 opens with a specific verb and resource: 'Add a Spline Mesh component to deform a Static Mesh along a two-point spline.' This clearly distinguishes it from generic spline components or instanced mesh tools, though it doesn't name sibling tools explicitly.

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?

It gives practical usage context—'Use SetStartAndEnd in the Construction Script' and 'Perfect for creating curved pipes, rails, fences, etc.'—but does not explicitly say when to avoid this tool or prefer add_spline_component for multi-point paths. The guidance is implied, not stated as an alternative.

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