Fix read-file from exploding with path not found error.

- There were a few hiccups here. Somehow 2.5-flash wasn't actually abiding by our tool schema. Instead it was inferring `path`. To semi-combat this I've renamed `file_path` -> `path`.
- We weren't elevating errors that were created via schema validation. Instead both the `glob` and `read-file.ts` now surface this.
- In error scenarios (like failing schema) we were improperly surfacing these as success cases because we were overriding tool status.

1 files changed, 2 insertions, 3 deletions

diff --git a/packages/cli/src/tools/read-file.tool.ts b/packages/cli/src/tools/read-file.tool.ts
index bbf9eafb..206267be 100644
--- a/packages/cli/src/tools/read-file.tool.ts
+++ b/packages/cli/src/tools/read-file.tool.ts
@@ -38,8 +38,7 @@ export class ReadFileTool extends BaseTool<ReadFileToolParams, ToolResult> {
    * Delegates validation to the core logic
    */
   validateToolParams(_params: ReadFileToolParams): string | null {
-    // Currently allowing any path. Add validation if needed.
-    return null;
+    return this.coreLogic.validateToolParams(_params);
   }
 
   /**
@@ -62,7 +61,7 @@ export class ReadFileTool extends BaseTool<ReadFileToolParams, ToolResult> {
   /**
    * Delegates execution to the core logic
    */
-  async execute(params: ReadFileToolParams): Promise<ToolResult> {
+  execute(params: ReadFileToolParams): Promise<ToolResult> {
     return this.coreLogic.execute(params);
   }
 }