Server defines 4 tools with basic schemas and descriptions. All tools have input schemas with type definitions and required fields. However, descriptions are minimal (10-150 chars, below the 194-char baseline), parameter descriptions are sparse or missing, output schemas are undocumented, and error handling lacks recovery guidance. Tool names lack action verbs (e.g., 'details' instead of 'get_preprint_details'). No parameter validation examples or constraints documented. Composition is reasonable (single responsibility per tool), but parameter naming could be clearer (e.g., 'date_or_range' is ambiguous vs 'date_start' and 'date_end').

• Rename tools to start with action verbs: 'get_preprint_details', 'list_published_preprints', 'search_by_publisher', 'get_submission_summary'. This matches the 90% baseline of A+ tools and helps LLMs infer intent from names alone.
• Add 50-100 char descriptions to every parameter. Example for 'date_or_range': 'Single date (YYYY-MM-DD) or range (YYYY-MM-DD/YYYY-MM-DD). Range is inclusive. Example: "2024-01-01" or "2024-01-01/2024-01-31".'
• Document output schemas in tool descriptions or a separate schema section. Example: 'Returns {preprints: [{doi, title, authors, date, journal}], total_count, next_cursor}'. This enables LLMs to extract and chain results.
• Enhance error messages with recovery guidance. Instead of 'interval must be "m" or "y"', return 'Invalid interval: got "x". Must be "m" (monthly) or "y" (yearly). Defaulting to monthly.'
• Split 'date_or_range' into explicit parameters or add enum constraint for 'server' values. Example: server: {type: 'string', enum: ['biorxiv', 'medrxiv']} instead of free-form string validation in callTool().