Server exposes 29 Telegram tools with consistent naming (verb_noun pattern: get_*, send_*, create_*, delete_*, etc.). All tools have descriptions (avg ~80 chars, baseline 194). Input schemas are present with type definitions and parameter descriptions. However, output schemas are NOT documented in the visible code, only input schemas appear in tool definitions. Error handling is minimal; no recovery guidance or actionable error messages visible. Parameter descriptions are brief (often 1-2 sentences) and lack constraint details (ranges, enums, format specs). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Missing: pagination guidance for list tools, field-level chaining IDs in responses, and dependency hints.

• Add output schema documentation to every tool. Use a 'returns' field in the tool definition or a separate schema registry. Example: get_me returns {id: int, username: string, first_name: string, ...}.
• Implement tool annotations. Map Risk levels to MCP hints: READ_ONLY → readOnlyHint=true, DESTRUCTIVE → destructiveHint=true, WRITE → idempotentHint=false (or true if the tool is idempotent).
• Formalize parameter constraints in JSON Schema. Replace informal descriptions like '(1-4096 characters)' with minLength/maxLength properties. Add enum constraints for parse_mode, notify, etc.
• Add pagination guidance to list tools. Document: 'Returns up to {limit} items. Use offset_id to paginate. Total count not provided; if result count equals limit, more items may exist.'
• Enhance error descriptions with recovery hints. Example: 'If chat not found, try get_entity() to resolve the username first. If rate-limited, wait and retry with exponential backoff.'

Inferred effective spec: 2026-07-28+.

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