Server has 29 tools with basic naming (verb_noun pattern mostly followed) but critical gaps in schema completeness and parameter descriptions. All tools visible in src/index.ts with explicit registration. Tool names are clear (get_*, create_*, update_*, delete_*) but parameter schemas are severely underdocumented. Most parameters lack detailed descriptions explaining format, constraints, or valid ranges. Output schemas are not documented. Generic 'body' parameters (tools 4, 6, 7, 10, 11, 13, 15, 23, 29) expose unstructured object types with minimal guidance. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. Tool descriptions are present but brief (10-50 chars typical), lacking context on when to use each tool vs similar ones.

• Replace all generic 'body' parameters with explicit object schemas. For create_address, define required fields (street, city, postcode, etc.) with types and descriptions. Use JSON Schema properties, not free-form objects.
• Document output schemas for all tools. E.g., get_shipment should return {uuid: string, status: string, recipient: {name, phone}, created_at: ISO8601, ...}. This enables LLMs to chain calls and extract IDs.
• Add error handling guidance to tool descriptions. E.g., 'Returns 404 if barcode not found, try search_shipment() with partial barcode. Returns 503 if API is down, retry after 30s.'
• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use get_last_status for quick status checks; use get_all_statuses to see full history'). Add prerequisites (e.g., 'Requires valid barcode from create_shipment').
• Add a confirm_delete_shipment tool or require a confirmation parameter (e.g., confirmed: true) for delete_shipment. Prevent accidental destruction of shipments.