Three tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling. All tools lack descriptions for their parameters (critical baseline violation: 100% of A+ tools have param descriptions). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). No output schemas documented. No error handling guidance. No tool annotations. Tools are read-only but lack idempotentHint declarations.

• Add parameter descriptions to all tools. E.g., web_search: 'query: The search query string (free-form text, e.g., "latest AI news")'. roll_dice: 'notation: Dice notation string (format: NdSideskN, e.g., 2d20k1 rolls 2d20 and keeps the highest 1)'. get_exchange_rate: 'currency_code: ISO 4217 currency code (3 uppercase letters, e.g., USD, EUR, GBP)'.
• Document output schemas. E.g., web_search returns a string (search results summary); roll_dice returns a string (formatted roll results); get_exchange_rate returns a JSON string with keys: base_currency, last_updated, exchange_rates (object of code→rate pairs). Add to docstrings or return type hints.
• Add error handling guidance to get_exchange_rate description: 'Returns error messages for invalid currency codes or network failures. If currency code is invalid, try search_currencies() first (not yet implemented) or consult ISO 4217 list.'
• Constrain roll_dice notation parameter. Update description: 'Dice notation string matching pattern NdS or NdSkK (N=num dice, S=sides, K=keep). E.g., 2d20k1, 3d6, 1d100. Invalid notation raises ValueError.'
• Add tool annotations via fastmcp if supported, or document in descriptions. E.g., 'This tool is read-only and idempotent, safe to call multiple times with the same input.'