Server has 17 tools with consistent naming (wb_ prefix) and descriptions present for all. However, descriptions are often terse (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented in the visible code. Tool annotations (ToolAnnotations import visible) suggest some metadata, but schema completeness is unclear. Error handling exists but recovery guidance is minimal. Composition is reasonable, tools are single-purpose, but parameter relationships and validation rules are underdocumented.

• Document output schemas for all tools. Include field names, types, and whether results are paginated. Example: 'Returns {suppliers: [{id: int, name: string, status: string}], total: int, next_cursor?: string}'.
• Expand parameter descriptions to 50 - 150 chars. For 'period', specify: 'Object with date_from and date_to (ISO 8601 format, e.g. {"date_from": "2024-01-01", "date_to": "2024-01-31"})'.
• Add pagination support to list/search tools. Include limit (default 20, max 100), offset/cursor, and total_count in responses. Document in tool description: 'Returns up to 20 results; use offset to paginate.'
• Enhance error messages with recovery hints. E.g., 'Supplier not found (ID: 12345). Call wb_list_suppliers() to see available suppliers.' instead of bare error codes.
• Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) to all tools. Mark wb_connect_supplier, wb_refresh_analytics, wb_upload_cost_price as destructiveHint=true; mark read-only tools accordingly.