This server has critical definition gaps. All 4 tools lack parameter descriptions entirely, a hard blocker per the rubric. Tool descriptions are minimal (10-20 chars), hitting the floor for description scoring. Schemas are present but sparse: 'greet' and 'listOrders' have empty property objects (no params documented), while 'echo' and 'getOrder' have single params with types but no descriptions. No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint, etc.). The codebase shows annotation infrastructure (@AiTool) but it's not being leveraged for parameter documentation. This is a skeleton implementation.

• Add descriptions to every parameter. For 'orderId', write: 'The order ID (e.g. ORD-001). Use listOrders() first to discover available IDs.'
• Expand tool descriptions to 50-200 chars. Example for listOrders: 'Retrieves all orders in the system. Returns order summaries with ID, status, and total. Call this first to discover available orders before fetching details.'
• Document output schemas for each tool. Specify field names, types, and what data they contain. E.g., listOrders returns [{orderId: string, status: string, total: number}].
• Add error handling guidance in tool descriptions. E.g., 'If orderId not found, returns 404 with available order IDs. Retry with a valid ID from listOrders().'
• Leverage the @AiTool annotation to add parameter-level documentation via a 'params' field or separate @AiParam annotations, then surface these in the schema generation.