chore(post): add summary

mkdocs/blog/posts/2024-12-02-go-tool.md

@@ -23,7 +23,7 @@ well.
 
 <!-- more -->
 
-## Giving it a spin with `gotip`
+## Giving this a spin with `gotip`
 
 You can try it out today using
 [`gotip`](https://pkg.go.dev/golang.org/dl/gotip):
@@ -82,7 +82,10 @@ You can now run tools like this:
 gotip tool <the-tool>
 ```
 
-And you can also see which bundled tools are available:
+And if you step out of the project, the tool you just added is no longer
+available.
+
+You can also see which bundled tools are available by default with Go 1.24:
 
 ```bash
 $ gotip tool
@@ -108,3 +111,15 @@ test2json
 trace
 vet
 ```
+
+## Summary
+
+I think this development is great, and it's something my colleagues and myself
+have been waiting for. At work, we are currently using our own flavour of tools
+management using [Sage](https://github.com/einride/sage) but more common
+approaches are to use a `Makefile` and/or a `tools.go` file.
+
+This new `go tool` workflow introduces less complexity (than the
+`Makefile`/`tools.go` setup) but it likely won't solve all the use cases, like
+splitting out test dependencies from the production dependencies or
+solve/improve integration with IDEs/editors.