Two tools with well-structured schemas and comprehensive parameter descriptions. koneps_search has detailed, LLM-optimized descriptions (50-200 char range) and proper enum constraints for service/business_type. Input validation is explicit (regex patterns, min/max bounds). However, output schema is not documented, the tool returns dict[str, Any] with no field specification. koneps_coverage lacks visible implementation details. Both tools are read-only and properly annotated. Missing: output schema documentation, error handling guidance, and recovery instructions.

• Document koneps_search output schema: specify fields returned (e.g., bid_id, title, organization, budget, deadline, link) with types and descriptions. Include pagination metadata (total_count, next_page_available).
• Add error handling guidance: document API rate limits, timeout behavior, invalid date range errors, and recovery steps (e.g., 'If date range is invalid, try narrowing to 24 hours').
• Expand koneps_coverage description to 50-100 chars: 'Returns which service-business_type combinations are supported. Call before koneps_search to validate your parameters.'
• Add result limiting guidance in koneps_search description: 'Returns up to max_pages × num_of_rows results. Default 20 results. For large result sets, use pagination and rank_by_fit to prioritize top matches.'
• Migrate to HTTP transport (Streamable HTTP or HTTP+SSE) to enable remote client access and hosted deployment.