This server has significant definition quality gaps. Tool descriptions are present but generic (avg ~80 chars, below the 194-char baseline). Input schemas are visible for most tools but lack proper type constraints and enums. Parameters like 'type' in get_investors and trigger_scrape lack enum constraints despite accepting known values ('Venture Capital', 'sec', 'sec_adv', etc.). Output schemas are not documented. Error handling is minimal, most endpoints return generic 500 errors without recovery guidance. The assess_signal and summarize_signal tools (tools 6-7) have minimal descriptions and no visible schema definitions in the source. No tool annotations (readOnlyHint/destructiveHint) are present despite clear read/write distinctions.

• Add output schemas to all tools. Document the structure of investors array, stats object, job response, etc. Use JSON Schema with typed fields and descriptions.
• Convert free-form 'type' parameters to enums. get_investors: ['Venture Capital', 'Family Office', 'Angel', ...]; trigger_scrape: ['sec', 'sec_adv', 'sec_13f', 'crunchbase'].
• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it, and key prerequisites. E.g., 'Fetch investors from Supabase with optional filtering by type, state, and focus areas. Supports pagination. Returns paginated list with total count.'
• Add actionable error messages. Instead of 'Failed to fetch investors', return 'No investors found matching filters. Try broadening search or removing state filter.' Include the invalid value and constraint violated.
• Add tool annotations: readOnlyHint=true for get_* tools; destructiveHint=true for create_investor and trigger_scrape; idempotentHint=true for get_* tools.