15 tools with Chinese descriptions and basic parameter schemas. Most tools have descriptions (10-50 chars, below the 50-200 char LLM-optimized baseline), and input schemas are present but minimal. Critical gaps: no output schemas documented, no error handling guidance, no tool annotations (readOnlyHint/destructiveHint), and parameter descriptions are sparse or missing. Naming is verb-forward (login, list, create, delete) but some tools like 'trash' and 'restore' lack clarity on reversibility. No evidence of idempotency guarantees or recovery patterns. Schemas show types but lack constraints (enums, ranges, patterns). This is a functional but immature implementation.

• Document output schema for every tool. E.g., create returns {doc_id: string, name: string, folder_id: string, created_at: ISO8601}. Include all fields downstream tools need.
• Expand descriptions to 50-200 chars with WHEN/WHY context. E.g., 'login' → 'Authenticate to Mubu using credentials from environment or interactive prompt. Required before any other operation. Returns session token.'
• Add tool annotations: mark list/get/search/trash as readOnlyHint=true; mark delete/purge as destructiveHint=true; mark create/save as idempotentHint=false (or true if safe to retry).
• Enrich parameter descriptions with constraints. E.g., folder: 'Folder ID (string, default "0" for root). Use list() to discover folder IDs.' content: 'Outline as JSON string matching Mubu schema. See export_tree() for example format.'
• Add error recovery guidance. E.g., delete tool: 'If doc_id not found, call search() to locate it. Requires yes=true to prevent accidental deletion.'

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

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