Single tool 'picui_api' exhibits poor design patterns. Tool name lacks action verb (should be 'upload_image', 'list_images', etc.). Description is generic Chinese text without actionable guidance for LLM selection. Schema is present but massively overloaded: 18 optional parameters crammed into one tool, many with unclear dependencies (e.g., 'file_path' marked optional but required for upload_image action). No parameter validation guidance, no error recovery hints, no output schema documentation. The tool violates single-responsibility principle by combining 8 distinct operations (get_profile, upload_image, delete_image, etc.) into one dispatcher. This forces the LLM to reason about which parameters apply to which action, increasing error likelihood.

• Split 'picui_api' into 8 separate tools: upload_image, list_images, delete_image, get_profile, generate_token, list_albums, delete_album, get_strategies. Each tool should have a single action, clear parameters, and documented output schema.
• For each tool, write descriptions following pattern: 'Uploads an image to PICUI. Requires file_path (local image path) and optional token (temporary upload token). Returns image URL and metadata. Fails if file not found or token expired, retry with fresh token via generate_token.'
• Add per-parameter validation rules in descriptions: 'num (integer, 1-100): number of tokens to generate' instead of just '生成Token数量'. Include constraints, ranges, and valid enum values.
• Document output schema for each tool. E.g., upload_image returns {status: bool, message: string, data: {url: string, key: string, ...}}. Include which fields are always present vs optional.
• Enhance error handling: catch httpx.HTTPError and return structured error with category (retryable|user_fixable|fatal), suggestion (e.g., 'Token expired. Call generate_token() to get a fresh one'), and the invalid value that caused the error.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry