My instructions to creating a modded tool does involve file editing

1. Create a folder named "Toolsets" located for "$CONTENT_DATA/Tools/Database/" If said "$CONTENT_DATA/" doesn't have "Tools" folder, then create a stream of Folders.
   
2. Add a file named "toolsets.tooldb" located for Tool Database. It's formatted in Json. From there, put:
   
   { "toolSetList": [ "$CONTENT_DATA/Tools/Database/Toolsets/example.json" ] }
   You don't have to put exactly "example.json", put as many files as you want.
   
3. In "Toolsets" folder, create and enter "example.json" or "example.toolset". It's also formatted in Json. From there, put:
   
   { "toolList": [ { "uuid": <string:UUID>, "previewRenderable": <string:path.rend>, "previewRotation": [ 1, 0, 0, 0, 0, -1, 0, 1, 0 ], "name": "example_tool", "scripted": { "file": <string:path.lua>, "class": "exampleClass", "data": {} } } ] }
   Of course, those arrow marks "<" and ">" are invalid for Json, but they're here for instruction purposes.

Create however much tools you'd like from here. Be sure to update toolsets.tooldb from time to time for managing your Tool sets.

If toolsets.tooldb exists, it'll add in tools from your mod

If you have no idea about what "$CONTENT_DATA" is, basically, it'd reference the root of your mod, the folder that's named how you named your mod originally, even if you've edited that name of those folders.

You don't have to do those first 3 steps from the instructions for Blocks and Parts, because that part is built in.

thx you make my day