Each tool targets a distinct resource or action: chat, model listing, model details, comparison, pricing, cost estimation, usage, connection test, config export, and presets. While list_models and get_model_info both relate to models, the former enumerates models while the latter provides detailed info for a single model, making the distinction clear. The descriptions reinforce these boundaries.

All tools follow a consistent aiorouter_ prefix with a verb_noun pattern: chat, list_models, get_usage, get_pricing, export_config, compare_models, etc. Naming is uniform, snake_case, and verbs align with the operation. No mixed conventions or vague verbs like 'do_thing'.

With 10 tools, the server is well-scoped for an AI router service. Each tool earns its place by covering distinct user needs: interaction, exploration, cost management, and configuration. This is within the ideal 3-15 range and neither feels sparse nor overwhelming.

The surface covers the core domain comprehensively: chat completions, model discovery (list, get, compare), pricing and cost estimation, account usage, connection validation, and configuration export. No obvious dead ends or missing essential operations for the stated purpose of interacting with AIOrouter. The only noted limitation (non-streaming) is a technical constraint, not a tool gap.