upgates-mcp demonstrates solid definition quality with consistent verb-noun naming, complete schemas with types and descriptions, and proper pagination support across all 16 read-only tools. All tools follow the 'list_/get_*' pattern clearly. Descriptions are present and functional but could be more LLM-optimized. No parameters lack type definitions. All tools include pagination metadata (page, current_page, number_of_pages, total_count). The server properly uses tool annotations (readOnlyHint=True) for all tools. Key strengths: schema completeness, consistent naming, pagination. Key weakness: descriptions average ~50-80 chars, below the 194-char baseline for A+ tools. Descriptions are primarily functional ('List orders...', 'Get a specific...') without dependency hints or when-to-use guidance. No error recovery documentation in descriptions.

• Expand tool descriptions to 100-200 chars. Example: 'list_orders' currently ~50 chars. Extend to: 'List orders from Upgates e-shop API. Filter by order number, dates, payment status, or fulfillment status. Returns paginated results (max 15 items per page); use page parameter to iterate. Customer PII is pseudonymized.'
• Add LLM selection hints to tool descriptions. E.g., 'get_invoice' should note: 'Use when you have a specific invoice number. To find invoice numbers, call list_invoices() with date or order filters first.'
• Document pagination truncation explicitly in descriptions for list_* tools. The server truncates results to 15 items per page. Tool instructions mention this, but the 10 list_* tools should each state: 'Results are limited to 15 items per page. Use page parameter to retrieve additional records. The field mcp_truncated=true indicates items were omitted from this page.'
• Add parameter constraints in descriptions using formal language. E.g., 'language must be an ISO 639-1 code (e.g., cs, en)' instead of relying on JSON Schema alone.
• Create a dedicated 'common_patterns.md' file documenting: (a) how to chain list_* and get_* tools (e.g., list_customers → get_customer); (b) GDPR pseudonymization behavior and when to use order/invoice numbers vs. customer emails; (c) pagination and truncation semantics. Link to this from all tool descriptions.