Single tool 'order-tickets' with moderate definition quality. Tool has a clear verb-noun name and a description present, but the description is verbose and contains example values (anti-pattern). Parameter descriptions are minimal (5-10 chars each). No output schema documented. No error handling guidance. No parameter constraints (e.g., quantity bounds, date format validation). Resource 'timeslots' is present and functional but similarly lacks detailed schema documentation.

• Replace example values in description with formal constraints. Remove '(timeslot: "April 19, 2025", quantity: 3)'. Instead, add to parameter descriptions: timeslot='ISO 8601 date string (e.g., 2025-04-19); must be a future date within 90 days', quantity='integer between 1 and 100, inclusive'.
• Document the output schema explicitly. Add to tool definition: 'Returns {content: [{type: "text", text: "Confirmation message with order number"}]}'.
• Add error handling guidance. Extend parameter descriptions: 'If timeslot is invalid or fully booked, the tool returns an error message suggesting available alternatives. If quantity exceeds inventory, retry with a smaller number.'
• Add bounds to quantity parameter. Update schema: z.number().min(1).max(100).describe('Number of tickets to order (1-100)').
• Clarify date format for timeslot. Update schema: z.string().describe('ISO 8601 date string (YYYY-MM-DD); must be a future date within 90 days from today. Example: 2025-04-19.').
• Shorten and refocus tool description. Current: 194 chars with example values. Target: 100-150 chars stating only WHAT (order tickets), WHEN (when user wants to book), and what the user needs (available timeslots from the timeslots resource). Remove implementation details.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry