Server has 17 tools with inconsistent schema quality. Most tools use z.any() for complex inputs (create_bill_payment, create_customer, create_employee, create_estimate, create_journal_entry, create_purchase), which provides zero type safety and forces LLMs to guess structure. Three tools (create_account, create_invoice, create_item) have well-defined Zod schemas with proper constraints. Descriptions are present but generic (avg ~60 chars), lacking WHEN/WHY context. No tool annotations (readOnlyHint/destructiveHint). Error handling returns text responses but lacks recovery guidance. No pagination support despite financial data likely returning large result sets. Tool naming is verb-first and clear, but parameter descriptions are minimal.

• Replace z.any() with explicit Zod schemas for create_bill_payment, create_customer, create_employee, create_estimate, create_journal_entry, create_purchase. Define required fields (e.g. VendorRef, Amount) and optional fields with clear types.
• Add destructiveHint annotation to all 5 delete_* tools. Agents need to know these operations are irreversible. Use tool.destructiveHint = true in registration.
• Expand descriptions to 100-200 chars. Include: (1) what the tool does, (2) when to use it vs similar tools, (3) key prerequisites. E.g. 'Create a bill payment in QuickBooks Online. Use after creating a bill with create-bill. Requires vendor reference and payment method.'
• Clarify delete_* parameter design: specify whether idOrEntity accepts a string ID, numeric ID, or full entity object. Provide examples in description. Consider splitting into delete_by_id and delete_by_entity if both are needed.
• Add error recovery guidance. Return structured errors with classification (retryable, user-fixable, fatal) and next steps. E.g. 'Error: Vendor not found. Try search_vendors() first to get a valid VendorRef.'