The server provides 6 well-intentioned tools for Korean R&D regulation search and retrieval. All tools have descriptions and basic input schemas with typed parameters. However, the definitions lack LLM-optimization depth, output schemas are not documented, and error handling is minimal. Tool naming is reasonable (verb_noun pattern), but parameter descriptions are sparse and do not guide LLM behavior effectively. The schema definitions are present but incomplete, parameters lack detailed type constraints, ranges, and format guidance that production tools require. Most parameters are documented at a surface level but lack the actionable constraints (enums, regex patterns, ranges) that prevent LLM hallucination. Output structure is mentioned in code comments but not formally specified in tool definitions.

• Add formal output schemas to all 6 tools. Document the structure of returned results: e.g. search_provision returns [{ provision_id: string, title: string, excerpt: string, relevance_score?: number }, ...], with explicit field types and whether fields are optional.
• Add min/max constraints to numeric parameters. Document 'limit' as '1 - 100 (default: 10)' and any query length limits. Use JSON Schema minLength, maxLength, minimum, maximum, enum, or pattern fields.
• Enhance parameter descriptions with format guidance. For 'section_id', state the pattern: 'Format: digits, letters, or hyphens (e.g., "1-1", "b1-2-3"). See list_rule_sets for valid section IDs.' For 'query', hint at valid input: 'Korean keywords or romanized Hangul (e.g., "기술료", "gisul-ryo").'
• Document error cases and recovery paths. Add to get_provision_detail: 'If provision not found, try search_provision to find the correct ID. If search returns no results, try suggest_review_sources for related regulations.'
• Add tool annotations (readOnlyHint: true) to all 6 tools since they are read-only. This signals to clients that results are safe to cache and retries are idempotent.
• Enhance list_rule_sets description: 'Returns all available rule sets (regulations, manuals, and supplementary documents). Call this first to discover valid identifiers for get_provision_detail and get_manual_section.'
• Add pagination guidance where applicable. If search results can exceed 50 items, document the limit parameter and clarify whether results are ranked by relevance or sorted by ID.

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

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