All 4 tools lack input parameter schemas (empty {} objects), violating the critical requirement that every tool must have a documented schema. Descriptions are present but minimal (20-60 chars), below the 50-200 char baseline for LLM-optimized descriptions. No parameter descriptions exist. Tools are read-only and simple, but lack the structure needed for reliable agent integration. Tool names follow verb_noun convention (get*), which is positive, but the absence of schemas and sparse descriptions severely limits usability.

• Add explicit input schemas to all tools. Even if no parameters are required, declare an empty object with proper JSON Schema: {"type": "object", "properties": {}, "required": []}.
• Expand tool descriptions to 80-150 characters. Example: 'Get the current Blue market USD/ARS exchange rate (unofficial parallel market). Use this for real-world transaction rates in Argentina. Returns price, timestamp, and source.'
• Document the output schema for each tool. Specify fields like: price (number), currency_pair (string), timestamp (ISO 8601), source (string), market_type (string).
• Add context to descriptions explaining when to use each rate type. E.g., 'Official rate is set by the Central Bank; Blue rate reflects the parallel market; MEP is the stock market rate; Cripto is the cryptocurrency exchange rate.'
• Add error handling guidance: 'If the rate is unavailable, the tool returns an error with a retry_after_seconds field. Retry after the specified delay or inform the user that rates are temporarily unavailable.'