This is a collection of 4 tools across multiple MCP server implementations. Critical issues across the board: 2 of 4 tools lack descriptions entirely (online_resercher, read_doc), parameter descriptions are either missing or trivial (null values), input schemas are present but minimally documented, and output schemas are not documented. The codebase shows multiple incomplete implementations with TODO comments indicating unfinished work. Tool naming has issues: 'online_resercher' is misspelled (should be 'online_researcher'), and parameter names lack sufficient context. No evidence of error handling guidance, idempotency patterns, or security considerations in the visible code. The server uses fastmcp with stateless_http=True, showing awareness of current patterns, but tool definitions themselves are immature.

• Add complete descriptions to 'online_resercher' and 'read_doc' (aim for 50 - 200 characters explaining what the tool does, when to use it, and what it returns).
• Fix tool name: rename 'online_resercher' to 'online_researcher' and update all references.
• Document all parameter descriptions with type, format, and constraints. For 'query': 'Web search query string (1-500 characters)'. For 'doc_id': 'Document identifier (one of: deposition.md, report.pdf, financials.docx, outlook.pdf, plan.md, spec.txt)'.
• Add output schemas to every tool definition. Example for read_doc_contents: 'Returns a string containing the document content.'
• For edit_document, implement a confirmation pattern: add a 'dry_run' parameter (boolean, default false) that previews changes without applying them, or require explicit confirmation before writing.
• Add error guidance: 'If doc_id not found, return "Document not found. Available docs: deposition.md, report.pdf, financials.docx, outlook.pdf, plan.md, spec.txt." This enables the agent to suggest corrections.'
• Complete the TODO implementations in mcp2, mcp3, and mcp4 servers. Ensure all tool functions are fully defined and tested before deployment.
• Consider adding a 'docs' or 'list_documents' resource to advertise available document IDs rather than hardcoding them in error messages.
• For online_resercher, add parameter constraints: 'query must be 1 - 500 characters; returns up to 10 results; results include url, title, snippet.'
• Add idempotency hints or a retry-safe mode to tools that call external services (online_resercher). Document whether repeated calls with the same input are safe.