I published n8n-nodes-vatnode , a verified n8n community node for EU VAT validation. One line in the node class, usableAsTool: true , also makes n8n generate an agent-facing Tool variant of it. That line is easy to add and easy to under-think, because it changes who reads your code. In a normal node the reader is a person looking at a canvas. In the tool variant, the reader of your descriptions is a model.
This article is about two things: what that flag does, as far as the types and n8n’s loader code show, and what the path to a verified node looks like when you build for it from the start. One limit up front: I have not run this node inside an agent or evaluated what an agent does with it. This covers how the tool variant is built, not agent behaviour.
What the Flag Does
usableAsTool is not described on the docs pages I checked (node base files, file structure, verification guidelines, submission).…