Single tool with basic implementation. Tool name follows verb-noun convention (summarize_wikipedia_article), but description lacks clarity on when to use vs alternatives, what fields are returned, and dependencies. Input schema present but minimal, single string parameter with description. No output schema documented. Error handling maps to MCP error codes but lacks recovery guidance. Tool does one thing well (summarization), but definition quality falls short of production baseline for three reasons: (1) parameter description is bare, lacks format/constraint details; (2) no documented output schema despite returning a string summary; (3) error messages are generic ('Unexpected error') rather than actionable recovery guidance. Description length ~180 chars is acceptable, but lacks WHEN/WHY context.

• Document the complete output schema. Instead of returning a bare string, consider returning a JSON object with fields: {summary: string, article_title: string, word_count: number, truncated: boolean}. This enables downstream tools to reason about quality and length.
• Enhance parameter description to include constraints: 'Wikipedia article URL (format: https://en.wikipedia.org/wiki/ARTICLE_TITLE). URLs must point to main article content. Redirects, disambiguation pages, and special pages are not supported. Max URL length: 2048 chars.'
• Add actionable error messages for each failure mode: (1) 'Invalid URL format. Must start with https://en.wikipedia.org/wiki/'; (2) 'HTTP error {status}. Verify URL is accessible and not behind a captcha.'; (3) 'Article structure not found. Ensure URL points to a standard Wikipedia article (not a redirect, talk page, or special page).'; (4) 'Summarization service unavailable. The Ollama model deepseek-r1:1.5b is not running. Ensure Ollama is started with this model available.'
• Document Ollama dependency and model availability in tool description. Add note: 'Requires Ollama running locally with deepseek-r1:1.5b model. If model is unavailable, tool returns error with retry guidance.'
• Add timeout behavior to description. Specify: 'Tool has a 10-second timeout for Wikipedia fetch and unknown timeout for Ollama summarization (typically 30-120 seconds depending on article length). If timeout occurs, user should retry or fetch article manually.'
• Add parameter validation examples to guide LLM usage: 'Example valid URLs: https://en.wikipedia.org/wiki/Python_(programming_language), https://en.wikipedia.org/wiki/India. Invalid: https://en.wikipedia.org/w/api.php, https://en.wikipedia.org/wiki/Special:Search'