Single tool with no input schema, no description, and no output schema documentation. The tool definition is minimal: @mcp.tool() decorator with empty parameter list and trivial return value. No parameter descriptions, no error handling guidance, no output structure. Fails nearly all definition quality baselines.

• Add a comprehensive tool description (50-200 chars): 'Retrieve details of a restaurant reservation from Resy, including restaurant name, date, time, party size, and confirmation status.'
• Define input schema with typed parameters. If the tool accepts a reservation ID or confirmation code, add it as a required string parameter with description and validation pattern.
• Document the output schema with typed fields: reservation_id (string), restaurant_name (string), date (ISO 8601), time (string), party_size (integer), status (enum: confirmed|pending|cancelled), confirmation_code (string).
• Implement actual Resy API integration in the tool body instead of returning 'Success'. Call the Resy API with the injected RESY_API_KEY and return structured reservation data.
• Add error handling with recovery guidance: 'Reservation not found. Verify the reservation ID and try again, or use search_reservations() to find available bookings.'