Each tool has a mostly distinct role: find_leads is a query-level search, scrape_company targets a single known site, decode_cloudflare_email is a narrow utility, and list_leads reads cached results. The main risk is overlap between find_leads and scrape_company, since both 'collect published contact details', but the descriptions make the bulk-vs-single distinction clear enough.

All four tools follow a consistent snake_case verb_noun pattern (find_leads, scrape_company, decode_cloudflare_email, list_leads). No mixing of conventions or vague verbs.

Four tools cover the core lead-generation pipeline (search, scrape, decode, list) without redundancy. It is on the lean side — a couple more operations would round it out — but nothing feels extraneous.

The create/scrape/read path exists, but there is no way to search or filter saved leads beyond 'most recent rows', no update/delete of entries, and no export or dedupe operation. These are workable gaps but real ones for a lead-management workflow.