Server has 3 tools with significant definition gaps. auth_status and auth_setup have basic schemas and descriptions, but descriptions are vague and lack actionable context. tool_help is a meta-tool with minimal utility for end users. No parameter descriptions for auth_setup's 'login' field. Schemas present but descriptions fail to explain WHEN to use each tool, WHAT happens on success, or recovery paths on failure. No output schemas documented. No error handling guidance. Naming is acceptable (verb_noun pattern) but descriptions are too generic to guide LLM tool selection effectively.

• Add explicit output schema to auth_status: document that it returns {valid: bool, profile: str, expires_in: int, expires_in_human: str, login: str, ...} with field descriptions.
• Expand auth_setup description to 100-150 chars: 'Save a Yandex.Direct OAuth token (y0_... or AQAA...) to a named profile. This writes credentials to disk and activates the profile for future calls. Requires a valid token from Yandex OAuth flow.'
• Add description to auth_setup 'login' parameter: 'Optional Yandex.Direct Client-Login (email or numeric account ID) to associate with this profile for audit/multi-account support.'
• Move parameter documentation from tool_help into inline descriptions. Remove the 'Call tool_help(...)' delegation, each tool must be self-documenting.
• Add error handling guidance to auth_status and auth_setup: 'If token is invalid or expired, call auth_setup with a fresh token. If network fails, retry after 5 seconds. If profile not found, check profile name spelling.'