Groundhog MCP has 4 tools with critical definition gaps. Tool descriptions are extremely sparse (most are 1-4 words), input schemas are either missing or incomplete, and parameter descriptions are absent. The `read_url` tool has a minimal schema with one parameter that lacks a description. The `research`, `search`, and `status` tools lack visible input schemas entirely. No output schemas are documented. Tools violate the baseline expectation that 94% of A+ tools have full docstrings and 100% have parameter descriptions. The codebase shows tool names via Dockerfile validation but actual tool implementation details are not present in the provided source, making it impossible to verify schemas beyond what appears in the Dockerfile comment. STDIO-only transport further limits production readiness.

• Expand each tool description to 50-200 characters explaining WHAT it does, WHEN to use it, and any prerequisites. E.g. 'Read and extract article text from a given URL, returning structured content with title, body, and metadata. Use before calling research() to analyze full-page content.'
• For read_url, add parameter description: 'url (string): A valid HTTP/HTTPS URL. Must start with http:// or https://. Relative URLs and file:// schemes are not supported. Example context: https://example.com/article'
• For search and research, document input parameters with type, description, and constraints. E.g. 'query (string, required): Search terms (2-500 characters). Use natural language; wildcards and regex are not supported.'
• For search tool specifically, document whether it returns web results, news, images, or a mix. State result limit and whether pagination is supported (offset/limit or cursor-based).
• Add output schema documentation for all tools. E.g. read_url returns {title: string, body: string, metadata: {author, date, language}, status_code: number}. This enables downstream planning.
• Document error cases and recovery strategies. E.g. 'If read_url returns status_code 404, the URL does not exist. If it returns 403, access is restricted. If it times out after 10s, try a simpler query or shorter content.'
• For search and research, specify whether they access real-time data or cached results, and what refresh rate applies.
• Clarify whether these tools use the Groundhog stealth browser (Chrome with anti-detection) or standard HTTP fetching, so LLMs understand when to call them.