Law7 is a STDIO-only legal document query server with 13 tools. Tool naming follows verb-noun convention and is clear (query-laws, get-law, search-regional-law, etc.). However, parameter and tool descriptions lack depth and context. Most tools have minimal descriptions (10-30 chars) that fail to explain WHEN to use the tool or HOW it differs from similar tools. No output schemas are documented in the visible code. Error handling is absent, no recovery guidance, classification, or actionable error messages shown. The server lacks tool annotations (readOnlyHint/destructiveHint). While tool definitions are explicitly visible in the tool files, the descriptions are insufficient for LLM reasoning. Average description length appears to be ~20-35 chars, below the 194-char baseline for A+ tools.

• Expand each tool description from ~20 chars to 80 - 200 chars. Include: (a) What the tool does, (b) When to use it vs similar tools, (c) A brief example of expected results, (d) Any prerequisites (e.g., 'Call list-countries first to see available codes'). Example: 'Query legal documents from the Russian Federal Database using semantic search. Use this for general law lookups; use search-regional-law for region-specific codes like KOAP. Returns matching articles with title, text preview, and amendment date.'
• Document output schemas for all 13 tools. Include field names, types, and constraints. Example for query-laws: '{results: [{id: string, title: string, text_preview: string, country: string, last_amended: ISO8601_date}], total_count: number, has_more: boolean}'
• Add parameter constraints to descriptions. For query-laws: 'limit: integer, 1 - 100 (default 20). Returned results capped at this value. country: 2-letter ISO code (e.g., ru for Russia) or omit for all countries.'
• Mark fetch-and-ingest with destructiveHint and idempotentHint guidance. Description should read: 'Fetch and ingest legal documents from official sources. WARNING: Ingesting the same document_url multiple times may create duplicates. Idempotency: if document_url is already in the database, this call is a no-op (returns success with cached ID).'
• Add readOnlyHint to all read-only tools (query-laws, get-law, list-countries, get-statistics, get-code-structure, get-article-version, trace-amendment-history, search-regional-law, get-regional-koap-article, search-court-decisions, get-supreme-court-resolution, search-interpretations). This signals to agents that these calls are safe to retry and have no side effects.

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

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