ossuno-mcp demonstrates solid fundamentals: all 5 tools have clear verb-noun names (list_*, upload_*, download_*, presign_*), detailed descriptions in Chinese (avg ~150 chars), and explicit JSON schemas with typed parameters. Tool annotations (destructiveHint, idempotentHint) are present and tested. However, descriptions lack English translations (barrier for non-Chinese LLMs), some parameter descriptions are sparse (e.g., presign_url's 'expires_seconds' lacks range guidance), and output schemas are not documented. Error handling guidance is minimal. Pagination support in list_objects is good (continuation_token), but no total count returned.

• Translate all tool descriptions and serverInstructions to English, or provide bilingual descriptions (Chinese + English). Use a format like 'List all buckets in the OSS account (bucket name, region, creation time). | 列出当前 OSS 账号下的所有 Bucket...'
• Document output schemas explicitly. For each tool, add a 'Returns' section describing the response structure, field types, and example values. E.g., 'Returns: {buckets: [{name: string, region: string, created_at: ISO8601}], total_count: integer}'
• Add range and constraint hints to parameter descriptions. E.g., 'expires_seconds: Link validity period in seconds (default 3600, max 604800 / 7 days). Must be positive integer.'
• Enhance list_objects response to include total_count or has_more flag so LLMs can estimate result set size and plan pagination.
• Add recovery guidance to tool descriptions. E.g., upload_file: 'If bucket not found, call list_buckets first. If overwrite fails, check bucket versioning status via list_buckets or OSS console.'