This server has critical definition gaps. All 4 tools have minimal descriptions (10-24 chars, well below the 50-200 char baseline for LLM-optimized tools). Parameter descriptions are sparse or missing entirely: 'size' and 'from' lack descriptions in both search tools; 'lens_id' has no description in either detail tool. Input schemas are present but incomplete, no type constraints, enums, ranges, or validation guidance. The 'query' parameter in scholarly_search has no description at all. Error handling is generic (401 → 'invalid or expired token') with no recovery guidance. No output schema documentation. Tool names are acceptable (verb_noun pattern) but descriptions fail to explain WHEN to use each tool or what distinguishes patents_search from patent, or scholarly_search from scholarly.

• Add 50-150 char descriptions to each tool explaining WHAT it does, WHEN to use it, and how it differs from related tools. E.g., 'patents_search: Search across millions of patents by title, abstract, or Lucene query. Use for broad discovery; call patent() to fetch full details by lens_id.'
• Add descriptions to all parameters: 'size' → 'Number of results to return (1-1000, default 25)'; 'from' → 'Pagination offset (default 0)'; 'lens_id' → 'Unique Lens.org identifier for the patent or scholarly work'.
• Document output schema for each tool. E.g., 'patents_search returns {total: number, results: [{lens_id, title, abstract, publication_date}]}' so LLM knows what fields to expect.
• Add validation and constraint descriptions: 'size must be 1-1000; values outside this range will be clamped.' Include format hints for lens_id (e.g., 'alphanumeric string, e.g., 123-abc-456').
• Enhance error messages with recovery guidance: 'Lens.org: 401, token invalid or expired. Get a free academic token at https://www.lens.org/lens/user/subscriptions and pass via PLATFORM_LENS_KEY environment variable or ?_apiKey parameter.'