gofetch

The two tools serve clearly different purposes: one performs the paid HTML extraction, the other returns free pricing/route metadata. There is no realistic scenario where an agent would confuse fetching content with looking up prices, and the descriptions reinforce the sequencing (call pricing first).

Both tools share a consistent `gofetch_` namespace prefix, which makes the set easy to recognize. The suffixes differ slightly in form (`extract` is a verb, `pricing` is a noun), a minor deviation from a strict verb_noun pattern but still readable.

Two tools is thin, even acknowledging that the service is deliberately a single-capability paid extraction API. One tool is a metadata/discovery helper rather than a real operation, so the actionable surface is effectively one call.

The core extract operation is fully specified (envelope, schema mode, payment behavior, error semantics), but there are notable gaps: no JS-rendered alternative route, no batch extraction, and no way to probe a URL's fetchability without paying or invoking the extract. Agents can work around these, but they are real limitations.