The Entscheidsuche MCP server provides two search/retrieval tools for Swiss case law. Both tools have basic descriptions and parameter definitions, but several critical issues reduce quality: (1) Tool descriptions are present but minimal (119-121 chars), failing to explain WHEN to use each tool or how they differ; (2) Parameter descriptions are generic and lack actionable constraints (e.g., 'size' has no clear upper bound guidance, 'format' enum is present but not explained in the parameter description); (3) No output schema is documented, forcing LLMs to infer structure; (4) Error handling is silent (try-catch blocks log nothing to the LLM); (5) Parameters lack format/range guidance beyond basic types. The tools are READ_ONLY and functional, but fall short of production-grade documentation expected for confident agent use.

• Expand tool descriptions to 150-200 chars and include a sentence on WHEN to use each tool. E.g., 'Use search_case_law to find decisions by topic or keyword. Use get_document to retrieve full text once you have a case signature from search results.'
• Document the output schema explicitly. For search_case_law, define: 'Returns object with summary (string) and results array. Each result has: signature (string), court (string), date (ISO8601), title_de/title_fr/title_it (string), abstract_de/abstract_fr/abstract_it (string), document_url (string).'
• Add constraint guidance to parameters: 'size: number between 1 and 50 (default 10). Requesting more than 50 will be capped.' Reflect this in zod schema as .min(1).max(50).
• Explain format parameter options: 'json: structured metadata (default); html: rendered HTML document; pdf: binary PDF (requires external viewer).'
• Improve error messages with recovery guidance: 'Signature not found. Ensure it matches the format from search results (e.g., CH_BGer_005_5F-23-2025_2025-07-01). Try search_case_law first if you only have keywords.'
• Clarify spider parameter: 'Optional. If omitted, extracted from the signature prefix (e.g., CH_BGer from CH_BGer_005_...). Provide explicitly if you know the court code (e.g., CH_BGer for Federal Supreme Court).'
• State pagination in tool description: 'Pagination: use 'from' parameter (0-indexed) to page through results. Each call returns up to 50 results.'
• Add idempotent and readonly hints to tool definitions via toolAnnotations (if supported by MCP SDK) to signal to agents that these are safe to retry.