BikeTheRail

Each tool targets a distinct access pattern: attribute/filter search (search_trails), geographic proximity (trails_near), single-record detail (get_trail), and closure status (list_closures). The descriptions explicitly cross-reference each other (slug from search_trails or trails_near), leaving no realistic path for misselection.

Three tools follow a clear verb_noun pattern (get_trail, list_closures, search_trails), which is easy to scan. trails_near deviates by leading with the noun, but it remains readable and semantically sensible for a proximity query.

Four tools is a tight, well-scoped set for a read-only trail reference API, with no redundancy. It sits just under the ideal range but each tool clearly earns its place.

The surface covers the core lifecycle of trail discovery: find by attributes, find nearby, fetch details, and check closures with sources. Minor gaps exist (no explicit state/region enumeration or bulk trail listing beyond filtered search), but agents can work around them via search filters.