add_get_actor_rotation_node

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

With no annotations, the description carries the full behavioral burden. It discloses the core behavior—adding a node and returning a Rotator in degrees—and the optional graph position, but it does not mention side effects on the Blueprint graph, whether the node is auto-connected, or any failure behavior. This is adequate but not rich.

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 core action is front-loaded in the first sentence, and the args/KB/example sections are compact and labeled. The 'Ch.14' sentence adds domain context but is not essential to using the tool; still, the overall size is reasonable.

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 two-parameter add-node tool with an output schema available, the description is largely complete: it includes the action, return type, parameter formats, a KB link, and a working example. It is only missing explicit guidance about when to choose this node tool over related siblings.

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 basic semantics for both args: blueprint_name is illustrated with a '/Game/...' path example, and node_position is defined as an optional [X, Y] graph position. However, blueprint_name itself is nearly tautological and the coordinate space/default behavior of node_position is not explained.

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 names a specific action and resource: 'Add a Get Actor Rotation node' and specifies its output type (Rotator with Pitch, Yaw, Roll in degrees). This makes it easy to distinguish from sibling node tools such as add_get_actor_location_node or add_set_actor_rotation_node.

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 no when-to-use guidance, no exclusions, and no reference to related alternatives. It only states what the tool does and provides an example call; an agent is left to infer when this node is appropriate versus siblings like add_actor_world_rotation_node.

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