A framework is a collection of tools to help you building web apps, just like a toolset for building shelves.

Your toolset also dictates the shape like a screwdriver dictates the shape of the usable screws.

The framework becomes part of the house, or cupboard. A screwdriver does not become part of the house.

That is the semantic difference between tools and frameworks.

This doesn't mean one cannot ever use a framework as a tool, or a tool as a framework. But I'd argue in those cases one stops being resp. a framework or tool and starts being a tool or framework.

They are still tools though.

Maybe the word 'tool' is just not adequate and there is no 1 to 1 equivalence here. If you come from woodworking, the saw or drill doesn't end up being part of the table you build whereas the framework code is part of the actual product you build. Or in other words, if you remove the framework after you programmed your solution the solution stops working where as if you remove the drill and put it back into your bag the table still stands. I would argue there is a categorical difference at play here.

So maybe words like tool, scaffolding (and even framework) are just not entirely up to the job of describing what a 'software framework' is and ultimately lead to confusion.

Tool is an adequate word, they just need to apply it correctly. Vim is a tool. It’s used for writing code.

A framework is not a tool. It is previous work that you build upon so you are not starting from scratch. It is a canvas, already assembled and sized.