Server has 9 well-named tools with consistent verb_noun patterns (wiki_get_page, wiki_create_page, wiki_delete_page). All tools have descriptions in Russian (10-200 chars, within baseline range). Input schemas are present with type definitions and parameter descriptions. Tool annotations (readOnlyHint, destructiveHint) are correctly applied. However, output schemas are not documented, LLMs cannot predict response structure for chaining. Error handling is minimal; no recovery guidance or actionable error messages visible in code. Parameter descriptions lack format constraints (e.g., slug pattern, content encoding). No pagination documented for wiki_tree and wiki_search despite returning lists.

• Document output schemas for all tools. Example for wiki_search: 'Returns {results: [{id: int, slug: string, title: string, excerpt: string}], total: int, page: int}'. This enables LLMs to extract page_id for downstream calls.
• Add pagination to wiki_tree and wiki_search descriptions: 'Returns up to page_size results (default 20, max 100). Include total_count and next_cursor in response for large datasets.'
• Implement error handling with recovery guidance. Example: 'If slug already exists, try wiki_search(slug) to find the existing page, then wiki_update_page() to modify it.'
• Add format constraints to parameters. slug: 'Alphanumeric + slash, e.g. homepage or razrabotka/deploy (max 255 chars)'. content: 'YFM-formatted text (max 1MB).'
• Add dry-run or confirmation pattern to wiki_update_page: 'Destructive operation. Consider calling wiki_get_page(page_id, with_content=true) first to review current content before replacing.'