Three tools with basic descriptions but significant schema and parameter documentation gaps. search_docs and sync_sources have minimal parameter descriptions (e.g., 'source' lacks detail on valid values). docs_status has no parameters but acceptable description. No output schemas documented. No error handling guidance. Tool names follow verb_noun pattern (search_, sync_, docs_) but descriptions are brief (10-30 chars) and lack context on when/why to use each tool. No parameter type constraints (enums, ranges) visible. No indication of idempotency, destructiveness, or recovery paths.

• Add formal output schemas for all three tools. Document search_docs return as {results: [{url, title, snippet, relevance_score}], total_count, next_cursor}. Document sync_sources and docs_status return as {state, coverage, complete, last_attempt_at, error?}.
• Expand tool descriptions to 50-150 chars with context: 'Search Upbit API documentation by keyword. Returns matching sections with URLs and snippets. Use before calling sync_sources to verify coverage.' Include when/why to use each tool.
• Convert 'source' parameter to an enum: {type: 'string', enum: ['upbit'], description: 'Documentation source (currently only Upbit supported)'}. Add validation and error message if other values are passed.
• Add error handling guidance: 'If search returns no results, try broader keywords or call docs_status to check cache freshness. If sync_sources fails, retry after 60 seconds (rate limit) or check network connectivity.'
• Document parameter constraints in descriptions: 'query (required): space-separated keywords, 1-100 chars. force (optional): if true, ignore ETag and re-fetch all documents (slower but ensures latest).' Add min/max length and format hints.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry