Two tools with clear verb-noun naming (search_posts, get_comments) and explicit JSON schemas. Descriptions are present and adequate (100-150 chars), meeting baseline minimums. However, parameter descriptions are sparse or missing entirely. The 'platform' enum is well-defined, but 'post_id', 'limit', and date parameters lack actionable guidance on format/constraints. Output schema is undocumented, LLMs cannot predict the structure of normalized posts/comments. Error handling is absent from the tool definitions. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.

• Add output schema documentation to both tools. Example for search_posts: 'Returns array of objects with fields: platform (string), id (string), author (string), text (string), likes (integer), replies (integer), date (ISO 8601 string), url (string). Platform-specific fields (e.g., subreddit for Reddit, plays for TikTok) may also be present.'
• Expand parameter descriptions. For 'post_id': 'The unique identifier of the post on the specified platform (string, required).' For 'limit': 'Maximum number of results to return (1 - 100, default 20).' For dates: 'Start date (YYYY-MM-DD, inclusive, UTC). Results include posts from 00:00:00 UTC on this date.'
• Add tool annotations to input_schema. Set 'readOnlyHint': true and 'idempotentHint': true for both tools to signal they are safe to retry.
• Document error scenarios in descriptions. Example: 'If the post_id does not exist, returns an empty array. If platform is invalid, raises an error with valid options: twitter, reddit, instagram, tiktok.'
• Clarify pagination and limits in tool descriptions. Example for search_posts: 'Searches up to 100 posts per call. Use start_date and end_date to narrow results across multiple calls if needed.'