add_get_actor_scale_node

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the node returns a Vector and that scale has X, Y, Z values, but it does not disclose side effects such as blueprint graph mutation, compile requirements, or behavior when the blueprint does not exist.

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 reasonably structured with a lead sentence, args, KB reference, and example. However, the 'Ch.14: Scale variable has X, Y, Z values. Use SetActorScale3D to modify.' lines are tangential to simply adding the node and add mild noise.

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 node-addition tool with two parameters and an output schema, the description is mostly adequate, providing an example and KB pointer. It lacks usage guidance and side-effect disclosure, but an agent could likely call it correctly for a known blueprint.

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 provides an Args section with brief semantics for both parameters, including that node_position is optional and is an [X, Y] graph position. The example clarifies that blueprint_name expects a full asset path, adding some 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 action: add a 'Get Actor Scale 3D' node and indicates the returned value is a Vector. It is specific about the node type, but it does not explicitly differentiate itself from sibling node-adding tools beyond the node name.

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 offers no explicit guidance on when to use this tool versus alternatives. The mention of 'Use SetActorScale3D to modify' hints at a related operation, but there is no clear context, exclusions, or selection criteria for when this node should be added.

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