Directional lights also need to create a small amount of off-axis illumination based on reflections and the light sourcing:

May 2014
https://feedback.bistudio.com/T98482

May also wish to apply volumetric effects to directional lights that are spawned in this way (such as flashlights) or enable the API support to drive them "on" or "off".
https://feedback.bistudio.com/T65741

At the request of a community member, adding prior establishment that the ability to do these directional lights is already in the engine.

"Tilion" established that "reflector" lights are in the engine with directional lightings as opposed to a "MarkerLight" which is an "orb" or "all-direction" light. At present, reflector lights have several properties which are attached via modification objects but are not yet available in scripting commands:

Quoting Tilion's post from 2013:

The memory point you assign to position parameter is where the light source itself will be. The one you put to direction is the way your light will shine. The cone itself is set using innerAngle, outerAngle and coneFadeCoef.

innerAngle sets the cone in which the light has it's full intensity.
outerAngle sets the cone outside of which the light has zero intensity.

coneFadeCoef is a coefficient that describes attenuation of the light between innerAngle and outerAngle. 1 equals linear attenuation, higher or lower value changes it, meaning how sharp/blurred will the edge of the lightcone as a whole be.
Note that both the angles represent full angle of the cone, not just "angular offset" from direction of the light. If you set it to 90 degrees, it means the cone is 45 degrees to the "left" and 45 to the "right" of the direction specified by your memory points.

In your case, having the direction memory point directly above the position means your light is pointed up in the sky. If you want an "all-direction" light, you might want to use MarkerLights instead of Reflectors (Reflectors are spotlights) that are configured somewhat similarly.