Five tools with complete, well-structured schemas and clear descriptions. Tool names follow verb_noun convention (exchange_rates, currency_rate, currency_history, monetary_aggregates, international_reserves). All descriptions are substantive (100 - 200 chars), explaining WHAT the tool does and WHEN to use it. Input schemas are properly typed with required fields marked. However, output schemas are NOT documented, LLMs cannot predict response structure. Parameter descriptions are good but lack explicit format constraints (e.g., 'YYYYMMDD format' is stated but not formalized as a pattern). No error handling guidance or recovery paths documented. All tools are READ_ONLY (safe), but this is not declared via toolAnnotations.

• Add formal output schemas to each tool. Document the response structure (e.g., 'Returns an array of objects with fields: r030 (number), txt (string), rate (number), cc (string), exchangedate (string in DD.MM.YYYY format).').
• Declare readOnlyHint: true in toolAnnotations for all five tools to signal idempotency and safety to LLMs.
• Replace prose date format descriptions with JSON Schema pattern: '^\d{8}$' to enforce YYYYMMDD at the schema level.
• Add error recovery guidance: 'If the date is invalid, ensure it is in YYYYMMDD format (e.g., 20240115). For historical data, use currency_history().'
• Remove example values from descriptions and move them to a separate 'examples' field or documentation. Replace 'e.g. USD, EUR, PLN' with an enum constraint or a link to ISO-4217 reference.