ShareBit AI MCP has 4 tools with basic descriptions and parameter schemas, but significant gaps in documentation and error handling. Tool names follow verb_noun convention (create, list, read, rename), which is good. However, descriptions are minimal (10-60 chars), parameter descriptions lack detail about constraints and formats, and output schemas are not documented. No error handling guidance, no parameter validation rules, and no security considerations visible. The plugin code (sharebit-ai.ts) is truncated, preventing full assessment of implementation quality.

• Expand tool descriptions to 50-200 chars. Example: 'sharebit_ai_create: Upload approved Markdown to ShareBit AI and return a private, temporary URL. Use this to share code snippets, logs, or documentation securely. Requires valid Markdown and an active ShareBit AI connection.'
• Add constraint details to parameter descriptions. For 'expires_in_seconds', specify: 'Lifetime in seconds (1 - 86400, default 1800). Pastes expire and become inaccessible after this duration.'
• Document output schemas for each tool. Example for sharebit_ai_list: 'Returns {pastes: [{id: string, title: string, created_at: ISO8601, expires_at: ISO8601, size_bytes: number}], total: number}'.
• Add error handling guidance. Example: 'If the paste ID is not found, the tool returns a 404 error. Suggest the user call sharebit_ai_list to find valid paste IDs.'
• Add parameter validation rules and enums where applicable. For 'title', specify max length (e.g., 256 chars). For 'limit', specify range (1 - 100, default 20).