Description
Problem
Having two tools for editing files takes up extra context for information unnecessarily and could semi-confuse models.
It also is a bit annoying to have to grant permissions for editing files twice in sessions (once for Edit, and again if multiple edits are wanted).
Solution
A simpler mental model would be to just have a single "Edit" tool that is in fact the Multi-Edit tool.
I see no reason personally for having two tools that do essentially the same thing when Multi-Edit covers all of the use-cases of Edit plus additional use-cases.
For simplicity's sake and for reducing context usage, a single tool seems sufficient.
Description
Problem
Having two tools for editing files takes up extra context for information unnecessarily and could semi-confuse models.
It also is a bit annoying to have to grant permissions for editing files twice in sessions (once for Edit, and again if multiple edits are wanted).
Solution
A simpler mental model would be to just have a single "Edit" tool that is in fact the Multi-Edit tool.
I see no reason personally for having two tools that do essentially the same thing when Multi-Edit covers all of the use-cases of Edit plus additional use-cases.
For simplicity's sake and for reducing context usage, a single tool seems sufficient.