Ax-Studio exposes 8 tools for proxy server and provider management via STDIO. Tool names follow verb_noun convention (start_server, stop_server, get_server_status, register_provider_config, etc.), which is positive. However, critical gaps undermine quality: (1) Descriptions are present but generic and lack actionable context, e.g., 'Start the proxy server with specified configuration' does not explain WHEN to call it, what prerequisites exist, or what happens on failure. (2) Input schemas are visible but incomplete: parameters lack type constraints (e.g., 'trusted_hosts' is array but no item type; 'models' is array with no schema). (3) No output schemas documented, LLMs cannot predict what these tools return. (4) No error handling guidance, tools do not indicate retryability, user-fixable vs. fatal errors, or recovery steps. (5) Security concerns: 'api_key' and 'api_key' parameters expose secrets as tool inputs, violating secret-injection pattern. (6) No pagination, no idempotency hints, no tool annotations (readOnlyHint/destructiveHint). Per-tool analysis: start_server and register_provider_config have the most complex schemas but still lack nested type definitions; stop_server and get_server_status are trivial (empty input). Overall, this is a functional but immature tool set that would require significant hardening before production use.

• Move api_key, api_keys, and any credentials to server-side environment variables or vault. Remove from tool parameters. Document how the server injects secrets internally.
• Document output schemas for all 8 tools. Specify return type (object/array/string), required fields, and field types. E.g., get_server_status should return {status: 'running'|'stopped', uptime_seconds: number, ...}.
• Expand descriptions to 100-200 characters. Include WHEN to call, prerequisites, and what happens on success/failure. E.g., 'Start the proxy server. Call this once before registering providers. Returns {status, port, uptime}. Fails if port is in use.'
• Add nested type definitions to array parameters. E.g., trusted_hosts: {type: 'array', items: {type: 'string', format: 'hostname'}}; models: {type: 'array', items: {type: 'object', properties: {name: {type: 'string'}, ...}}}.
• Add error handling guidance to descriptions. E.g., 'Fails if port is in use (retryable with different port) or if API key is invalid (user-fixable). Returns {error, code, suggestion}'.