Scoring was not performed

• Document output schemas for all tools. For each tool, specify the JSON structure agents will receive: field names, types, whether fields are optional, and which fields are safe to pass to downstream tools. E.g., kaito_sentiment should return: { date: string, sentiment_score: number, volume: number, notable_events: array }.
• Remove example values from descriptions and parameter docs. Replace 'e.g. BTC, ETH' with a formal constraint or enum. Replace date example '2024-01-01' with 'ISO 8601 date string (YYYY-MM-DD)'.
• Add validation and actionable error messages. When token lookup fails, return: 'Invalid token: XYZ. Valid tokens include: BTC, ETH, SOL. See the tokens resource for a complete list.' This matches pattern:recovery-guide.
• Specify minimum/maximum for numeric parameters. E.g., top_n in kaito_kol_token_mindshare should state 'default: 100, valid range: 1-1000' to prevent absurd values.
• Clarify mutually exclusive parameters. E.g., in kaito_smart_followers, user_id and username are listed as optional but one is required, state 'one of user_id or username is required' explicitly.
• Add pagination guidance. For tools returning lists (kaito_advanced_search, kaito_market_smart_following, kaito_mindshare_arena), document whether there is a next_cursor or if 'from' parameter supports pagination and what the total count is.
• Document API rate limits in a prompts resource or tool description footnote. E.g., 'Kaito API rate limit: 5 requests/second. Retries will be rate-limited with 429 responses.' This matches pattern:error-classification.