Use a short verb and object: “Parse incoming CSV,” “Reject missing IDs,” or “Send approved summary.” These names tell a reader what changes at each step. Avoid generic labels such as “Tool 3” or “Output” when the graph has multiple branches.
For outputs, include the format and purpose, such as “JSON rows for import.” Use the same term for the same data throughout the workflow, and mark steps that have external side effects. Read only the node names from start to finish; if the process is still understandable, the labels are doing useful work.
Names cannot replace a contract, so document required inputs and failure behavior as well.
Akousa