Strong specialized domain server for Japanese law. All 14 tools have explicit schemas and descriptions. Tool names follow verb_noun patterns (search_law, get_law, get_toc, etc.). Descriptions are detailed and domain-specific, ranging 100-450 chars, well above the 10 - 1024 baseline. Input schemas are comprehensive with proper JSON Schema typing. However, output schemas are not documented (no structured field descriptions for what these tools return). Error handling emphasizes graceful degradation (search_fulltext falls back to search_law, verify_citations returns per-item results without blanket failure) but lacks recovery guidance in descriptions. Tool parameters are well-described with constraints (enums for format/file_type, required fields clear). One composition weakness: several tools (get_law, get_law_range, get_law_revisions) operate on the same law_name resource, differentiation is clear from names but could be emphasized. Parameters like 'at' (point-in-time version) and 'depth' (hierarchical limit) show domain sophistication. Security: no credentials exposed; all read-only tools with appropriate risk classification.

• Document output schemas for all 14 tools. For each, publish the structure of the return value: field names, types (string/number/object/array), required fields, and one example. Use a structured format (JSON Schema or prose table) visible in tool definitions or docs.
• For get_law_range, formalize the mutual-exclusivity constraint in the inputSchema using a discriminated union or explicit validation note. Alternatively, add an example in description: 'You must specify exactly one of: part+chapter+section (or suppl_index), or path, or suppl_index.'
• Add enum or pattern constraints to article/paragraph/item parameters. If formats like '8', '8の2', '第8号の2' are valid, state the regex pattern (e.g., pattern: '^(第)?\d+([の漢字]+)?$') in the schema, not just the description.
• Expand all tool descriptions to include recovery hints. Example: 'If law_name is not found, try resolve_abbreviation(abbr) first, or search_law(keyword) to discover the exact name.'
• Add a note to list_attachments description: 'Call this before get_attachment to discover available files. Pass src (file ID) from the result to get_attachment.'
• Consider adding optional tool annotations (readOnlyHint: true for all; idempotentHint: true for search and get tools) to make intent clearer to agents. This is a small bonus but not required by the current spec.

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

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