Restaurant Voice Agent defines 10 tools with basic schemas and descriptions. All tools have names starting with action verbs (search_, get_, add_, remove_, update_, check_, compute_, confirm_, cancel_) and descriptions present. However, descriptions are terse (10-50 chars for most), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Tools like add_order_item and confirm_order handle state changes but lack explicit error guidance or confirmation patterns. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present. Schema completeness varies: search_menu and get_menu_item have basic type info, but check_dietary_info conflates three concerns (allergen check, dietary question, item lookup) in one tool. Composition issues: add_order_item, remove_order_item, and update_order_item could be unified into a single order_item management tool. Parameter naming is inconsistent: session_id vs item_id vs line_item_id. No pagination support on search_menu despite potentially large result sets.

• Expand all tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. Example: 'search_menu: Search the restaurant menu by item name or category. Returns up to top_k matching items with ID, name, price, and description. Use this to help customers find dishes matching their preferences.'
• Document output schemas for all tools. For search_menu, specify: returns array of {item_id, name, price, category, description}. For add_order_item, specify: returns {line_item_id, item_id, quantity, modifications, special_instructions, unit_price, line_total}.
• Split check_dietary_info into two tools: check_allergen(item_id, allergen_name) and check_dietary_restriction(item_id, restriction_type). Each tool has one clear responsibility.
• Add tool annotations: mark search_menu, get_menu_item, get_order_summary, compute_total with readOnlyHint=true; mark confirm_order, cancel_order with destructiveHint=true; mark add_order_item, remove_order_item, update_order_item with idempotentHint=false (or true if they support idempotency keys).
• Add pagination to search_menu: accept limit (default 20, max 100) and offset parameters; return total_count and has_more.