This collection aggregates 17 tools across multiple OSINT domains (finance, social media, email intelligence, web scraping). While tool names follow verb_noun conventions and most have descriptions, critical gaps undermine quality: (1) Many descriptions lack actionable context for LLM selection, e.g., 'Get stock information' doesn't explain WHEN to use it vs. get_historical_stock_prices. (2) Parameter descriptions are sparse or generic; e.g., 'The ticker symbol' lacks format guidance. (3) No visible output schemas documented, LLMs cannot plan downstream calls. (4) Error handling is absent; no recovery guidance. (5) Security concerns: Hunter tools expose API key injection via env vars in mcp.json, and no rate limiting visible. (6) Tool composition issues: hunter_domain_search, hunter_email_finder, and hunter_email_verifier overlap significantly without clear differentiation. Baseline: 549 production tools average 194-char descriptions and 100% have documented return types; this collection shows ~60 chars avg and zero documented schemas.

• Document output schemas for all tools. For each tool, specify: response type (object/array), field names, types, and which fields are required for chaining. Example: 'Returns {ticker: string, price: number, timestamp: ISO8601, currency: string}'. This enables LLMs to plan multi-step calls.
• Expand tool descriptions to 100-200 chars following the WHAT/WHEN/WHY pattern. Example: 'Get real-time stock price and trading volume. Use this when you need current market data; for historical trends, use get_historical_stock_prices instead. Returns current price, volume, and market status.'
• Add per-parameter format constraints and examples in descriptions. E.g., 'ticker (string, 1-5 uppercase letters, e.g. AAPL)' and 'period (one of: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max; default 1mo)'. Replace free-form descriptions with enums where applicable.
• Implement error handling with recovery guidance. Return structured errors: {error_code, message, recovery_action}. Example: 'Invalid ticker INVALID_SYMBOL. Try search_tickers(query) to find valid symbols, or check ticker format (1-5 uppercase letters).'
• Move API keys to environment variables only (not mcp.json). Use server-side secret injection: read HUNTER_API_KEY from os.environ at startup, never expose in config files. Document required env vars in README with setup instructions.