OpenLive Gateway exposes 4 tools with minimal schema documentation. Tool definitions are scattered across JavaScript and Rust files without centralized registration. Only web_search and calculator have visible input schemas (single string parameter each); get_time and identity lack explicit schema definitions in the source. Descriptions are present but generic (10-40 chars), well below the 50-200 char LLM-optimized baseline. No parameter descriptions, no output schemas, no error handling guidance. Tools lack verb-noun naming clarity (identity is ambiguous). No evidence of tool annotations, pagination, or composition patterns.

• Expand all tool descriptions to 50-200 characters. Example: 'web_search' → 'Search the web for current information, news, and facts. Use when the user asks about recent events, product details, or factual lookups not in your training data.'
• Add parameter descriptions for all inputs. Example: 'query' → 'Search query string (1-500 chars). Can include keywords, phrases, or natural language questions. Special operators: site:domain.com, -word to exclude.'
• Document output schemas for each tool. Example: web_search returns {results: [{title, url, snippet, date}], total_results: number, search_time_ms: number}.
• Rename 'identity' tool to 'get_identity' or 'describe_self' to follow verb_noun convention and clarify intent.
• Add error handling guidance. Example: 'If web_search returns no results, try broader keywords or different phrasing. If calculator returns NaN, check expression syntax.'