Critical failures across naming, descriptions, and schemas. 20 tools with minimal documentation: most descriptions are 1-2 sentences (avg ~40 chars, well below 194-char baseline). Duplicate tool names (Read/FileRead, Edit/FileEdit, Write/FileWrite, WebFetch/Web_Fetch, WebSearch/Web_Search, NotebookEdit/Notebook_Edit) indicate poor composition and confuse LLM selection. Parameter schemas present but descriptions are generic ('Path to the file to read'). No output schemas documented. No error handling guidance. TodoWrite has EMPTY input schema. Tools lack verb-noun clarity (e.g., 'Read' vs 'FileRead', which should the LLM choose?). No pagination, no result limits, no chaining IDs in responses. Security: Bash/Shell/PowerShell execute arbitrary commands with no validation, sanitization, or permission gates.

• Eliminate duplicate tools. Choose one canonical name per operation: read_file (not Read/FileRead), write_file (not Write/FileWrite), edit_file (not Edit/FileEdit), fetch_url (not WebFetch/Web_Fetch), search_web (not WebSearch/Web_Search), edit_notebook (not NotebookEdit/Notebook_Edit). Use verb_noun naming consistently.
• Expand all descriptions to 100 - 200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and any prerequisites. Example: 'Read file contents from the filesystem. Use this to inspect code, configs, or logs. Requires valid file path; returns raw text or error if file not found.'
• Define output schemas for every tool. Document field names, types, and what data is returned. Example for read_file: {type: 'object', properties: {content: {type: 'string'}, size_bytes: {type: 'number'}, encoding: {type: 'string'}}}.
• Add input validation and error guidance to Bash/Shell/PowerShell. Reject dangerous patterns (rm -rf, dd, etc.). Return actionable errors: 'Command failed: permission denied. Verify you have write access to /path/to/file.' Support dry-run mode (--dry-run flag) for destructive operations.
• Define TodoWrite input schema with required parameters (e.g., title, description, priority). Add descriptions for each parameter. Document output (e.g., todo_id, created_at).