Server provides 6 tools with basic schemas and descriptions. All tools have descriptions (10-50 chars, below ideal 50-200 char range). Input schemas are present but minimal: most parameters lack individual descriptions. Tools 5-6 (ADNL endpoints) have empty input schemas ({}), violating schema completeness. No output schemas documented. Error handling absent, no recovery guidance or categorization. Tool naming follows verb_noun pattern (getHttpEndpoint, getAdnlProxyEndpoint) but descriptions are terse and lack context on when to use each variant. No parameter-level descriptions visible in schema definitions.

• Expand tool descriptions to 50-200 characters. Example: 'Get a single HTTP endpoint for TonCenter API v2. Use this when you need one endpoint for load balancing. For multiple endpoints, call getHttpEndpoints() instead.'
• Add individual descriptions to all nested parameters in the config object. E.g., 'network: Network to connect to (mainnet for production, testnet for development; default: mainnet)'.
• Document output schemas for all tools. Specify returned fields: endpoint URL, node ID, health status, weight, backend name, etc. Include example response structure.
• Add error handling guidance. Document what errors can occur (invalid network, unsupported protocol combination, no healthy endpoints available) and suggest recovery steps.
• For tools 5-6 (ADNL endpoints), define input schema even if empty. Use 'properties: {}' with a description explaining why no parameters are needed, or add optional parameters if the API supports them.