The Pizza MCP server defines 9 tools with reasonable naming conventions and mostly complete schemas. All tools use verb_noun naming (get_*, place_*, delete_*) which follows the agentic pattern. However, descriptions are brief and lack strategic guidance for LLM tool selection. Parameter documentation is present but inconsistent in depth. Output schemas are not explicitly documented. Error handling guidance is absent. The server demonstrates foundational quality but lacks the polish and completeness expected of production-grade tools.

• Document output schemas for all 9 tools. For example, 'get_pizzas returns {pizzas: Array<{id: string, name: string, price: number, description: string}>}'. This lets LLMs plan downstream calls (e.g., passing pizzaId to place_order).
• Expand tool descriptions to 80 - 160 characters. Include WHEN to call (e.g., 'Call before placing an order to see available pizzas'), and WHAT it returns (e.g., 'Returns a list of pizzas with id, name, price, and description.').
• Add error handling guidance to descriptions. Example: 'If pizza ID is not found, error will include a list of valid pizza IDs. Call get_pizzas() to discover available options.'
• For get_orders, document 'last' parameter format explicitly: 'Duration in format Nd, Nh, Nm (e.g., 60m, 2h, 7d). Invalid formats return error with examples.'
• Add constraints to place_order quantity: 'quantity must be between 1 and 100 per item. Orders exceeding limits will fail.'
• Add idempotency documentation to place_order and delete_order_by_id. Example: 'Calling place_order twice with the same userId and items within 5 seconds returns the same order. Safe to retry on transient failures.'
• Clarify optional parameter behavior. For get_toppings category: 'If omitted or empty string, returns all toppings. If specified, returns only toppings matching that category.'
• Consider adding pagination support to get_pizzas, get_toppings, get_orders if these lists can grow large. Include limit and offset/cursor parameters, and document result count.

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

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained