The server defines 5 read-only banking tools with basic structure, but has significant gaps in parameter descriptions, output schema documentation, and error handling guidance. All tools are present and have descriptions, but lack the depth and completeness expected for production use. Tool names follow verb_noun convention well (get_*, check_*), but parameter documentation is sparse. Output types are visible in code but not formally documented in schemas. No error recovery guidance is provided. The codebase shows dual implementations (main.py with FastMCP and main_manual.py with manual registration), the evaluation focuses on main_manual.py as it explicitly shows tool schema registration.

• Define formal output schemas for all 5 tools. For get_customer_info: return {customer_id: str, name: str, email: str, phone: str, branch: str, account_number: str}. For get_order_details: return {order_id: str, customer_id: str, order_date: str, status: str, total: float, items: [{name: str, quantity: int}]}. Document these in tool registration.
• Enhance parameter descriptions with format and constraints. E.g., customer_id: 'The customer ID in format CLI### (3 digits, e.g. CLI456)' vs current 'ID do cliente (ex.: CLI456)'. Use pattern constraints in JSON Schema if format is rigid.
• Add error recovery guidance. When a customer is not found, suggest: 'Customer not found. Try get_customer_ids_by_name() with the customer name.' When no orders exist, offer: 'No orders found. Use check_inventory() to see available products.'
• Extend tool descriptions to disambiguate selection. E.g., get_customer_info: 'Retrieve full banking profile (name, email, phone, branch, account) for a known customer ID. Use get_customer_ids_by_name() first if you only have the name.' And get_customer_ids_by_name: 'Lookup all customer IDs matching a full name. Call this first if you need to find a customer by name, then pass the ID to get_customer_info().'
• Add pagination to check_inventory and get_orders_by_customer_id. Add optional limit (default 20, max 100) and offset (default 0) parameters. Return {total: int, items: [...], limit: int, offset: int} so LLMs know when more results exist.
• Return structured JSON instead of plaintext. Modify get_customer_info, get_order_details, and check_inventory to return typed objects with named fields. LLMs can extract data reliably without parsing free text.