PaperMate has 4 tools with basic functionality but significant quality gaps. All tools have descriptions and visible input schemas, but descriptions lack depth and fail to follow agentic tool patterns. Parameters are minimally constrained (only 'query' string across 3 search tools). The add_term tool has the most complete schema with three typed parameters and a character constraint, but no error guidance or recovery patterns. None of the tools have documented output schemas, making downstream composition difficult. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Error handling is minimal, tools return raw exceptions rather than actionable recovery guidance. Tool descriptions are generic and don't answer WHEN to use each tool over alternatives (e.g., why arxiv_search vs tavily_search vs searxng_search?). Parameter descriptions are trivial ('Search query or term to look up' repeated 3 times).

• Differentiate search tools in descriptions: 'arxiv_search: Queries the official arXiv API for peer-reviewed preprints and published papers. Best for technical computer science, physics, and math terms. Returns structured metadata (title, authors, URL) for 3-5 results.' Similar explicit guidance for tavily_search (web + academic indexing) and searxng_search (local SearXNG instance, useful for offline or privacy-sensitive searches).
• Document all output schemas. For arxiv_search, declare: 'Returns a formatted string containing up to 5 entries. Each entry includes: title (string), authors (comma-separated string, up to 150 chars), summary (string, up to 400 chars), URL (string). Entries separated by double newlines.'
• Add maxLength, minLength, and pattern constraints to query parameter in JSON Schema. E.g., minLength: 1, maxLength: 200, pattern: '^[a-zA-Z0-9\s\.\-(),]*$' to prevent injection attacks.
• Add tool annotations to tool specs: arxiv_search and others should include 'readOnlyHint': true. add_term should include 'destructiveHint': true.
• For add_term, move the '50 chars max' constraint into JSON Schema: 'explanation': {'type': 'string', 'description': 'Brief explanation/definition of the term', 'maxLength': 50}.
• Enhance error messages with recovery guidance. Instead of 'Empty query', return 'Empty query. Please provide a search term (e.g., "Transformer", "attention mechanism", "BERT").' Instead of 'arXiv search error: ...', return 'arXiv API is unavailable. Try tavily_search or searxng_search instead.'

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

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