Tool4lm provides 22 tools across 11 functional areas (calc, web, doc, schema, wiki). Most tools have descriptions and visible schemas. However, several critical gaps emerge: (1) tool naming mixes dot and underscore conventions creating duplicate aliases rather than genuine alternatives; (2) descriptions are terse (10-50 chars) and lack 'when to use' guidance; (3) parameter descriptions are sparse or missing entirely; (4) error handling is absent from visible code; (5) output schemas are completely undocumented, we see tools return JSON but cannot verify structure from source. The server shows effort toward definition quality but falls short of production readiness. Average per-tool score: 62/100.

• Remove underscore aliases entirely. Use ONLY the dot-notation names (calc.eval, web.search, etc.). If the LLM struggles with dot notation, add ONE canonical snake_case name globally, not per-tool. This reduces cognitive load by half.
• Expand tool descriptions to 50 - 150 chars with the pattern: '[Verb] [resource] to [action]. Returns [result type]. Use this when [scenario], not [similar tool].' Example: 'Search academic databases (arXiv, Crossref) for papers by title/author. Returns ranked list of DOI, title, authors, date. Use this for scholarly research; use web.search for general information.'
• Document all output schemas. For web.search, specify: { results: [ { title, url, snippet, source } ], count: number, hasMore: boolean }. Include per-field descriptions.
• Add enum constraints and ranges to parameters. Example: engines should be an enum ['searxng', 'duckduckgo'] not a free-form array. max should have min=1, max=100, default=10.
• Add error handling examples in tool descriptions. Example for web.fetch: 'Returns {success: false, error: "timeout", retryAfter: 5} on timeout. Returns {success: false, error: "blocked_ssrf_range"} if URL is internal IP. Retry idempotent calls with exponential backoff.'
• Verify all handler code uses all declared parameters. web.fetch handler ignores timeout and max_bytes, either use them or remove them from schema.
• Add 'requires_network' or 'requires_local_files' annotations to tool descriptions to guide agent planning. E.g., 'Requires network access and SearXNG instance running at configured URL.'

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

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