add_get_rotation_at_distance_along_spline_node

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly states this operation adds a node to a blueprint and describes the node's runtime behavior (returns rotation at a distance). It also adds useful context about coordinate space and pairing with the location node, which goes beyond a bare 'Add node' statement.

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 and front-loaded: the core action comes first, followed by a one-line explanation, pairing context, parameter list, knowledge base pointer, and a concrete example. Each section earns its place, and there is no redundant filler.

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 add-node operation with four parameters and an output schema, the description is complete. It covers every parameter, provides a usage example, cites relevant knowledge base material, and describes the node's purpose and pairing behavior. Nothing essential for calling the tool correctly is missing.

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%, but the description lists and explains all four parameters: blueprint_name, spline_component_variable, coordinate_space with the allowed values 'Local' or 'World', and node_position as [X, Y]. This fully compensates for the schema's lack of property descriptions.

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 states a specific verb and resource ('Add a GetRotationAtDistanceAlongSpline node') and immediately explains what the node does: returns the rotation at a specified distance along the spline. It also distinguishes itself from the sibling node GetLocationAtDistanceAlongSpline by noting they are paired for orienting instances along the spline direction.

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 gives clear context for when to use this node: when you need rotation at a distance along a spline, paired with GetLocationAtDistanceAlongSpline to orient instances. It does not explicitly list exclusions or alternative tools, but the pairing and purpose provide enough guidance for selection.

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