baileys-mcp has 8 well-named tools with consistent verb_noun patterns (send_text, list_groups, parse_bid). All tools have descriptions (avg 95 chars) and input schemas with type definitions. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present and correct. However, parameter descriptions are sparse or missing context. send_image accepts both imageUrl and imageBase64 but lacks guidance on mutual exclusivity. list_messages and resolve_jid lack output schema documentation. Error handling is minimal, no recovery guidance or actionable error messages visible in handlers. Missing pagination details for list_groups and list_messages despite caching architecture.

• Document output schemas for all 8 tools. For list_groups, specify: {groups: [{jid: string, subject: string, participants: number}], total: number}. For auth_qr: {qr: string, expiresAt: number}. For connection_status: {connected: boolean, jid: string, uptime: number}.
• Add mutual exclusivity guidance to send_image: 'Provide either imageUrl OR imageBase64, not both. If both are provided, imageBase64 takes precedence.' Consider splitting into send_image_url and send_image_base64 for clarity.
• Enforce and document pagination for list_groups and list_messages. Add optional limit (default 20, max 100) and offset parameters. Return {items: [...], total: number, hasMore: boolean} to enable agent-driven pagination.
• Add error handling with recovery guidance in tool handlers. Example: 'Failed to send message to {to}: {error}. Verify the JID format ([email protected]) or call resolve_jid() first.' Categorize errors as retryable (network) vs user-fixable (invalid JID).
• Constrain parse_bid currencyHint to enum: ['ZAR', 'USD', 'EUR', 'GBP']. Update description: 'Currency code for bid parsing. Valid: ZAR (default), USD, EUR, GBP. Affects decimal/thousand separator interpretation.'