Critical failures across all dimensions. Tool definitions lack input schemas (cannot verify in source), descriptions are minimal (10-50 chars, well below 50-200 char baseline), and no parameter descriptions visible. All 10 tools show identical structural deficiencies. No error handling guidance, no output schemas documented, no security considerations (API tokens in env vars only). Naming is acceptable (verb_noun pattern) but insufficient to overcome schema/description gaps. Average across 10 tools yields ~28.

• Add full JSON Schema input definitions for all 10 tools. Include type, description, enum constraints, and min/max for each parameter. Example: { 'prompt': { 'type': 'string', 'description': 'Image generation prompt (1-2000 chars, no URLs)', 'minLength': 1, 'maxLength': 2000 } }
• Expand tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it, and key prerequisites. Example: 'Generate images via Midjourney AI. Use for creative visual content. Requires ACEDATACLOUD_API_TOKEN. Returns image URL and metadata. Timeout: 60-300s.'
• Document output schemas for all tools. Specify returned fields (e.g., image_url, generation_id, status, metadata). Include pagination info for serp_search (total_results, next_cursor).
• Add error handling guidance. For each tool, document common failures and recovery steps. Example: 'If timeout (>300s), retry with shorter prompt. If rate-limited (429), wait 60s before retry.'
• Implement parameter validation and return actionable error messages. Example: 'Invalid mode: got "turbo", must be one of: fast, standard, quality' instead of generic 400 errors.