Tide has 18 tools with significant definition gaps. Most tools lack visible input schemas in the provided source (only skill and install_skill show complete schemas). Descriptions vary widely: skill and install_skill are well-written (100+ chars, actionable), but 16 builtin tools (copy_path, create_directory, delete_path, list_files, glob, grep, move_path, read_file, write_file, replace_in_file, run_command, get_command_output, web_fetch, web_search, todo_write, spawn_agent) have no visible schema or description in the source code provided. Per HARD SCORING RULES, tools without visible schemas score 0 on schema dimension. This drags the average significantly. The two well-defined tools (skill, install_skill) score ~75 each; the 16 undefined tools score ~20 each (inferred existence, no visible definition). Average: (75+75+20*16)/18 ≈ 42.

• Add complete input and output schemas to all 16 builtin tools. Each schema must include type, description, and constraints (minLength, maxLength, enum, pattern) for every parameter.
• Write 50 - 200 character descriptions for each tool explaining WHAT it does, WHEN to use it, and any prerequisites. Example: 'read_file: Read and return the full contents of a text or binary file. Use to inspect code, configs, or logs. Returns {content, size, encoding, mimeType}.'
• Add parameter descriptions to every input. For 'path' params, clarify: 'Absolute or relative file system path. Must exist and be readable.' For 'pattern' params: 'Glob pattern (e.g., *.js, src/**/*.ts). Anchored to current working directory.'
• Implement confirmation or dry-run for destructive tools (delete_path, run_command, spawn_agent). Example: add a 'confirm' boolean param or return a 'confirmation_required' result requiring user approval before executing.
• Document output schemas for all tools. Example for list_files: '{files: [{name, path, size, type}], total_count, has_more}'. For run_command: '{exit_code, stdout, stderr, duration_ms}'.