Four tools with clear verb-noun naming (search_viral, trending_*) and reasonable descriptions (100-150 chars). All tools have input schemas with types and descriptions. However, output schemas are not documented, LLMs cannot see what fields to expect in responses. Parameter descriptions lack detail on constraints (e.g., 'limit' has no min/max stated). No error handling guidance. Missing tool annotations (readOnlyHint, idempotentHint). Virality scoring logic is sophisticated but not exposed to the agent for transparency.

• Document the ViralPost output schema in each tool's description or as a separate schema field. Include all fields: platform (enum), id (string), title (string), url (string), author (string), createdAt (unix timestamp), score (number), comments (number), viralityScore (0-100 number).
• Add enum constraints to 'platforms' parameter in search_viral: ['reddit', 'hackernews', 'x']. Add min/max to 'limit' parameters: min 1, max 50, default 15.
• Wrap API calls in try-catch with actionable error messages. E.g., 'Reddit search failed: query too broad, try a more specific keyword' or 'Hacker News API temporarily unavailable, retry in 30 seconds'.
• Add tool annotations via MCP SDK: mark all four tools with readOnlyHint=true and idempotentHint=true to signal safety to agents.
• Validate TWITTERAPI_IO_KEY at server startup and return a clear error in trending_x if missing: 'Twitter API key not configured. Set TWITTERAPI_IO_KEY environment variable to enable trending_x.'.