halfwhere

Each tool has a distinct input shape and purpose: two locations (halfway), a coordinate (near), and a name/postcode (suburb lookup). The mild ambiguity is between find_places_halfway and find_places_near, since both return the same venue category, but the descriptions make the selection criteria (two endpoints vs. a point) reasonably clear.

All three tools use a consistent find_<object> pattern with snake_case: find_places_halfway, find_places_near, find_suburb. The prefix and style are predictable, so an agent can infer new tool names.

Three tools is at the low end but each covers a genuinely separate step (geocode, midpoint search, point search) with no filler. The surface is tightly scoped to a single purpose rather than padded or overly thin.

The core flow of resolve-a-place then find-venues is covered, but notable gaps exist: no travel-time or transport-mode option for the 'halfway' computation, no reverse lookup from coordinates to suburb, and no in-API support for three or more participants (only a redirect to the website). Agents will often hit these dead ends.