Server has 11 tools with schemas and descriptions present, but quality is inconsistent. Naming follows verb_noun convention well (archive_chat, ban_user, create_channel). However, descriptions are often terse (10-50 chars) and lack actionable context for LLM selection. Parameter descriptions are sparse or missing entirely. Many tools lack output schema documentation. Error handling guidance is absent. Destructive operations (ban_user, delete_chat_folder, create_group) lack confirmation patterns in schema. No evidence of pagination support for list operations. Tool composition is reasonable but some operations combine multiple concerns (create_supergroup with photo + topics).

• Expand all tool descriptions to 50-200 characters. Include WHAT, WHEN, and any prerequisites. Example: 'Archive a chat to hide it from the main list without deleting messages. Use when you want to declutter but preserve history. Archived chats can be unarchived later.'
• Document output schemas for all tools. Specify which fields are returned, their types, and which IDs/references can be passed to downstream tools. Enable LLM chaining.
• Add parameter descriptions for all fields. For numeric parameters (color_id, folder_id), specify valid ranges or enums. For arrays (pinned_chats, included_chats), clarify format (IDs vs names) and limits.
• Implement error recovery guidance. When 'confirmed' is false/missing on destructive ops, return a clear message: 'This operation is destructive. Set confirmed=true to proceed.' Do not fail silently.
• Add pagination to list_chat_folders: accept limit (1-100, default 20) and offset/cursor parameters. Return total_count and next_cursor in response. Document in description.

Inferred effective spec: 2025-06-18+.

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