AgentDeals demonstrates solid definition quality with well-structured tools across 5 offerings. All tools have descriptions (range: 138 - 284 chars, well within the 10 - 1024 baseline), action-verb names, and documented parameter schemas. Schemas are comprehensive with enums, typed fields, and clear descriptions. However, output schemas are not explicitly documented in the source code, only inferred from descriptions. Error handling guidance is minimal. Pagination parameters are present where appropriate (limit/offset), and tool composition is clean (each tool has a single, clear responsibility). The server targets developer-tool discovery and stack planning, a specialized domain where the definitions align well with use cases.

• Document output schemas for all five tools. Show example response structures: search_deals returns array of {vendor, tier, description, url, stability, payment_protocols}; plan_stack returns {stack: [{service, vendor, tier, cost_per_month}], total_cost, risks}. This enables LLMs to extract and chain data correctly.
• Add error handling guidance to tool descriptions. E.g., 'If no results match your query, try broadening category or removing filters. If a vendor is not found, search_deals with a partial name to discover the canonical name.'
• Replace example queries in search_deals with formal enum/pattern constraints. Move 'Does Supabase have a free tier?' from description to capability statement or hidden example. Document the exact behavior: does 'query' support wildcard matching?
• Document plan_stack 'scale' object schema explicitly: 'Object with optional fields: monthly_requests (int), monthly_api_calls (int), storage_gb (float), bandwidth_gb (float), concurrent_users (int). All numeric fields default to 0 if omitted.'
• Clarify get_referral_code vendor matching: 'Vendor name, exact or fuzzy match (e.g., "supabase" matches "Supabase Inc"). If no match, returns error with available vendors in same category.'
• Add pagination guidance to search_deals description: 'Default limit is 20. Use offset to paginate large result sets. Returns total count so LLM can determine if more pages exist.'
• Document compare_vendors return structure and stability assessment methodology: 'Returns comparison table with pricing tiers, risk levels (stable/watch/volatile/improving), and recent changes. Risk is inferred from pricing-page change history.'