Each tool has a fairly distinct role in the pipeline (raw fetch, signal extraction, scoring, FAQ extraction), and score_presence explicitly documents its input dependency on extract_signals. However, fetch_page and extract_signals both fetch page content, and FAQs are listed as a signal inside extract_signals while also being the sole purpose of extract_faqs, which creates moderate overlap.

All four tools follow a clean snake_case verb_noun pattern: fetch_page, extract_signals, score_presence, extract_faqs. No mixed conventions or vague standalone verbs.

Four tools is slightly thin but fits a narrow, focused audit pipeline where each tool maps to a pipeline stage. Supporting optional parameters on score_presence (signals vs url, manual overrides) keep the count low without losing capability.

The core sequence fetch → extract → score is covered, but the surface has no way to persist or export an audit result, batch or compare multiple businesses, or re-fetch signals for a saved business. These are notable gaps for an audit workflow that otherwise looks self-contained.