gnews-mcp has clear, action-oriented tool names (search_news, ticker_news, top_stories, read_article) and concise descriptions (avg 115 chars, within 10-1024 range). All 4 tools have input schemas with type definitions and parameter descriptions. However, output schemas are undocumented, LLMs cannot predict response structure. Parameter descriptions lack format constraints (e.g., 'limit' has no min/max bounds stated). Error handling returns raw error strings without recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite all being read-only operations. Composition is sound: each tool has one responsibility, and search_news/ticker_news/top_stories feed into read_article naturally.

• Document output schemas for all tools. E.g., search_news returns {headlines: [{title: string, link: string, pubDate: string}], query: string, count: number}. This enables LLMs to extract fields correctly.
• Add min/max constraints to 'limit' parameter descriptions: 'Max headlines (default 10, min 1, max 50).' Consider adding JSON Schema minValue/maxValue properties.
• Enhance error messages with recovery guidance. E.g., instead of 'fetch article: context deadline exceeded', return 'Article fetch timed out (20s). URL may be slow or unreachable. Try a different article or check the URL.'
• Add readOnlyHint annotation to all 4 tools in mcp-go registration (e.g., mcp.WithReadOnly(true)) to signal safety to agents.
• Document read_article partial failure modes: 'Returns empty string if page is JavaScript-rendered or paywalled. Returns partial text if only some paragraphs are accessible.'