swiggy-cli exposes 8 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~80 chars). All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented, LLMs cannot predict response structure for downstream chaining. Error handling is minimal; no recovery guidance or actionable error messages visible. Parameter descriptions lack format constraints (e.g., date format, coordinate ranges). No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Composition is sound (single responsibility per tool), but missing pagination details and field-level documentation.

• Document output schemas for all tools. Example: get_addresses returns {addresses: [{id, fullAddress, category, ...}], total, page, pageSize}. This enables LLMs to extract addressId for downstream calls.
• Add tool annotations: mark delete_address with destructiveHint=true, create_address/create_cart with idempotentHint=false (or true if safe to retry), all read tools with readOnlyHint=true.
• Constrain parameters: latitude/longitude descriptions should state '±90 and ±180 respectively'; date should specify 'ISO 8601 (YYYY-MM-DD) or Unix seconds'; limit should state 'max 30'.
• Document create_cart parameter dependencies: 'For DEAL_TICKET_PURCHASE: slotId, itemId, reservationTime, guestCount required. For DINEOUT: billAmount, source required. Omit unused params.'
• Add recovery hints to descriptions: 'If address not found, call get_addresses() to list saved addresses.' 'If restaurant not found, try search_restaurants_dineout() with a broader query.'