Resolve the path in context
A relative path such as docs/guide.md is interpreted from a working directory, which may differ between tools or tasks. Check the tool description and current workspace root rather than assuming the path is relative to the file you are viewing.
Use exact spelling, extension, and directory names, especially on systems where case or special characters matter. If a path comes from user input, treat it as data and validate that it resolves inside the intended workspace before applying a change.
Verify the target before and after
For read-only inspection, confirm that the returned file name and contents match the intended target. For edits, inspect the diff and make sure neighboring files were not selected by an overly broad pattern.
Avoid paths containing credentials or private information in logs and reports. If a file has moved, locate the current version first; recreating a second copy at a plausible path can leave the project with conflicting sources of truth.