Critical gaps across all dimensions. Tool definitions lack input schemas entirely, cannot verify parameter types, constraints, or descriptions. No tool descriptions visible in registry or tool files. Tool names use generic verbs (explore, generate, run, fix) without clear object/action pairing. No output schemas documented. Error handling and recovery guidance absent. This server fails basic definition quality standards.

• Add explicit input schemas to all tools with typed parameters, constraints (enums, min/max), and descriptions. Example: exploreTool should declare url (string, required), depth (integer, 1-5), max_pages (integer, 1-100).
• Write 50-200 character descriptions for each tool explaining WHAT it does, WHEN to use it, and WHAT it returns. Example: 'Explore a website by crawling links up to specified depth. Returns list of discovered URLs and page metadata. Use before generating tests to understand site structure.'
• Rename tools to verb_noun format: explore_website, generate_test_suite, run_tests, fix_failing_tests, write_tests, read_tests, get_test_status. This makes intent clear from the name alone.
• Document output schemas for each tool with field types, required fields, and pagination info. Example: exploreTool returns {urls: string[], page_count: number, total_discovered: number, next_cursor?: string}.
• Add error handling with actionable recovery guidance. Example: 'URL not reachable. Verify the URL is correct and the site is online. Try a different URL or check network connectivity.'