The server provides 3 tools with explicit schemas and descriptions. Tool names follow verb_noun convention (web_search, read_file_info, read_file) which is good. However, there are significant gaps: descriptions are minimal (10-120 chars, below the 50-200 char LLM-optimized range), parameter descriptions are sparse, and output schemas are completely undocumented. The read_file and read_file_info tools have name ambiguity (both deal with file operations, distinction unclear from names alone). Error handling is not documented. No evidence of parameter validation guidance or constraint documentation (e.g., chunk_size ranges, max_file_size enforcement logic). The tools are read-only which is good from a security perspective, but no explicit permission gates or scope declarations are present.

• Expand tool descriptions to 100-200 characters. Include: what the tool does, when to use it (vs similar tools), prerequisites, and what data it returns. Example: 'web_search: Search the web via DuckDuckGo. Use when you need current information, external sources, or to verify facts the model doesn't have. Returns up to 10 results with title, URL, and snippet. Supports num_results 1-50.'
• Document output schemas for all tools. Specify field names, types, and meaning. E.g., web_search returns [{title: string, url: string, snippet: string, ...}]; read_file returns {content: string, size_bytes: integer, ...}.
• Add numeric bounds to parameters: num_results (1 - 50), chunk_size (1 - 1048576), max_file_size (1 - 10737418240). State units (bytes) explicitly.
• Add parameter validation guidance: path must be absolute or relative within configured base dir; disallow symbolic links and ../traversal patterns.
• Rename read_file_info to get_file_metadata for clarity and to distinguish from read_file.
• Document error cases and recovery: 'File not found' → suggest parent dir listing or similar filenames; 'DuckDuckGo API error' → retry in 5s; 'File exceeds max_file_size' → use read_file with force_streaming=true.
• Declare tool scope/permissions: all three tools are read_only; no write/delete permissions needed. State this explicitly so agents can be configured with least privilege.
• For read_file, document behavior of streaming vs concatenation threshold and when force_streaming overrides it. Explain why an agent would choose this parameter.

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

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