The Pantry MCP server provides 4 tools with varying quality. All tools have descriptions and input schemas, but several issues reduce quality significantly: (1) descriptions lack WHEN/WHY guidance that helps LLMs decide tool selection; (2) parameter descriptions are minimal (many under 72 chars baseline); (3) output schemas are not documented; (4) no error handling guidance for destructive operations; (5) the update_pantry_item tool has optional parameters without clear defaults or side-effect documentation. Tool names follow verb_noun conventions (add_, remove_, update_, get_) which is good. Schemas are present but lack completeness, expiration_time is marked optional without explaining defaults, quantity format is vague ('could be weight/volume/number'). The remove_from_pantry tool is marked DESTRUCTIVE but has no confirmation pattern or dry-run option documented.

• Add explicit output schema documentation to all tools. For get_pantry: 'Returns array of PantryItem objects with fields: {name: string, general_name: string, quantity: string, expiration_time: ISO8601 date or null, time_added: ISO8601 date}'. For add_to_pantry: 'Returns {status: 'success'|'error', added_items: [{name, general_name, quantity}], timestamp: ISO8601}'.
• Convert quantity parameter to enum or pattern constraint. E.g., quantity description: 'Numeric value with unit: 1lb, 2cups, 3oz, etc. Pattern: /^[0-9]+(\.[0-9]+)?(lb|kg|cups|oz|ml|l|g|etc.)$/, unit required.' Or provide enum_units: ['lb', 'kg', 'cups', 'oz', 'ml', 'l', 'g'] with quantity as number.
• Add 'WHEN to use' context to each tool description. E.g., add_to_pantry: 'Call this after scanning a receipt or after grocery shopping to add new items to inventory. For updates to existing items, use update_pantry_item instead.' remove_from_pantry: 'Use this to remove items that have been consumed or discarded. This is permanent, no undo. Consider using update_pantry_item(quantity=0) if you want to mark items as depleted instead.'
• Implement confirmation pattern for remove_from_pantry. Add a dry-run option or explicit confirmation requirement. E.g., add optional parameter 'confirm: boolean' with description 'Must be true to proceed. Set to false to preview what would be removed without deleting.'
• Document defaults for optional parameters in update_pantry_item. E.g., 'If quantity is omitted, existing quantity is unchanged. If name is omitted, existing name is unchanged. If both omitted, tool returns error: at least one field required.' Consider making at least one required.