Spring Boot AI server with 7 banking tools. All tools have descriptions (10-50 chars, mostly adequate) and visible input schemas with typed parameters. Naming follows verb_noun convention (freezeCard, unfreezeCard, openDispute, etc.). However, descriptions are terse and lack context about when to use each tool, prerequisites, or side effects. Parameter descriptions are minimal (e.g., 'The account identifier' repeated across tools). No output schemas documented. Error handling is absent, no guidance on what happens on failure or how to recover. No pagination support for listDisputes or getTransactions despite returning lists. Missing idempotency hints for write operations.

• Expand tool descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it, and side effects. Example: 'Freeze the card for an account to prevent unauthorized transactions. Use when fraud is suspected. This is irreversible until unfreezeCard is called.'
• Document output schemas for all tools. Specify return types and fields. E.g., freezeCard returns {success: boolean, message: string, frozenAt: ISO8601}.
• Add error handling guidance to descriptions. E.g., 'Returns null if dispute not found. Call listDisputes first to verify the dispute exists.'
• Add pagination to listDisputes and getTransactions: include limit (default 20, max 100) and offset parameters. Return total count in response.
• Add idempotency hints to write operations. Document that freezeCard is idempotent (calling twice with same accountId is safe). Consider adding a dry_run parameter to openDispute.