Server implements 3 read-only tools with clear action verbs (get_*, search_*) and valid JSON Schema. Tool descriptions exist but lack depth and do not follow LLM-optimized guidance. Parameter descriptions are present and mostly adequate, though some lack format/constraint details. Output schemas are not explicitly documented. Error handling provides basic recovery hints but is not comprehensive. The server follows a single-responsibility principle (law lookup, paragraph retrieval, fulltext search) which is sound, but descriptions do not anticipate LLM selection criteria or downstream usage. No security or permission issues detected (read-only operations only).

• Rewrite tool descriptions to follow the pattern: 'Tool does X. Use it when Y. Returns Z (type). Example: when you need to list laws before retrieving a specific paragraph, call this first with an optional law filter.' Current descriptions assume the LLM already knows the workflow.
• Document the output schema for each tool. E.g., get_lawlibrary should say: 'Returns a JSON array of objects with {abbreviation: string, full_name: string, url: string}' or whatever the actual structure is. Do this in the docstring, not just in code.
• Add constraints to parameter descriptions. For 'law' parameter, specify: 'Law code abbreviation (case-insensitive, 2-8 uppercase letters, e.g. BGB, HGB, SGB_V for SGB V). Must match an available law; call get_lawlibrary() first to discover valid values.' For 'paragraph', add: 'Paragraph number (1-4 characters: digits 0-9 and optional trailing letters a-z, e.g. 2, 14a, 1b).'
• Add pagination to search_laws. Accept 'limit' (default 20, max 100) and 'offset' (default 0) parameters. Return an object with {results: [...], total_count: N, has_more: boolean}. Document the limit in the tool description.
• Implement structured error responses. Instead of returning plain strings, return JSON objects with {error: string, error_code: string, recoverable: boolean, suggestion: string}. E.g., if law not found: {error: 'Law ABC not found', error_code: 'LAW_NOT_FOUND', recoverable: true, suggestion: 'Did you mean AGB? Call get_lawlibrary(law="AB") to search for similar laws.'}
• Add idempotent hints to tool schemas. All three tools are read-only and idempotent. Use MCP 2026-07-28 tool annotation: readOnlyHint=true for all tools. This tells the agent these tools are safe to cache and retry without side effects.