Four tools with clear verb-noun naming (whoami, resolve, list_chats, get_chat) and good descriptions (avg 120 chars, well above 10-char minimum). All tools have input schemas with type definitions. However, parameter descriptions are sparse or missing entirely: 'peer' and 'limit' lack descriptions; 'fields' array has no item-type specification. Output schemas are undocumented, LLMs cannot infer what fields list_chats or get_chat return. No error handling guidance. Tool composition is sound (each does one thing), but schema completeness and parameter documentation fall short of production baseline.

• Document output schemas for all tools. For list_chats, specify: returns array of {id, name, kind, unread_count, last_message_preview}. For get_chat, specify: returns {id, name, kind, username?, member_count?, description?}. Include which fields are always present vs optional.
• Add descriptions to all parameters. 'peer' → 'A @username, phone number, numeric id, or "me" to identify the chat'. 'limit' → 'Number of chats to return (1 - 200, default 20)'. 'fields' → 'Array of field names to include (e.g. ["id", "name", "unread_count"]).'
• Add error handling guidance to tool descriptions. E.g. resolve: 'If peer is not found, returns error with available matches. Try a partial @username if exact match fails.'
• Specify min/max for numeric parameters in schema. list_chats limit: minimum 1, maximum 200, default 20.
• Add dependency hints to descriptions. resolve: 'Call this first if you only have a @username or phone number. Returns a chat id for use in other tools.' get_chat: 'Requires a peer identifier; use resolve() first if you only have a username.'