Wordnik MCP has complete input schemas for all 12 tools with proper JSON Schema structure and required fields. No parameter descriptions exist anywhere, LLMs cannot infer what 'wlmi', 'sourceDictionaries', or 'limitPerRelationshipType' mean. No output schemas are documented. Tool names lack action verbs (e.g., 'definitions' instead of 'get_definitions', 'examples' instead of 'get_examples'). No error handling guidance, no pagination info, no API key injection pattern documented. The server exposes API key handling via _apiKey parameter (anti-pattern: secrets in params). Baseline: avg tool description 194 chars; this server averages ~8 chars. Baseline: 100% of A+ tools have param descriptions; this server has 0%.

• Expand all tool descriptions to 50 - 200 characters. Example: 'definitions' → 'Get word definitions from Wordnik. Returns definitions with part-of-speech, source dictionaries, and optional related words. Requires word parameter.'
• Add descriptions to every parameter. Example: 'limit' → 'Maximum number of results to return (1 - 100, default 20).' 'wlmi' → 'Weighted log mutual information threshold for phrase filtering (0 - 100).'
• Rename tools with action verbs: definitions→get_definitions, examples→get_examples, related→get_related_words, phrases→get_phrases, pronunciations→get_pronunciations, hyphenation→get_hyphenation, frequency→get_frequency, word_of_the_day→get_word_of_the_day, random_word→get_random_word, random_words→get_random_words, search→search_words.
• Move API key to server-side injection. Read from WORDNIK_API_KEY environment variable at startup. Remove _apiKey parameter. Document in README: 'Set WORDNIK_API_KEY before starting the server.'
• Document output schemas and add pagination guidance. Example: 'Returns array of definition objects with fields: text (string), partOfSpeech (string), source (string). Results capped at 100; use limit and skip for pagination.'