二行程經典車資料庫

find_part and search_models are distinct entry points (part vs. model), but get_model_specs already includes maintenance data and parts cross-reference, overlapping with get_maintenance and partially with find_part. The descriptions help, but an agent may still hesitate between the broad spec tool and the narrower maintenance/part tools.

All tool names follow a consistent snake_case verb_noun pattern: find_part, get_maintenance, get_model_specs, search_models. The convention is predictable and readable throughout.

Four tools is reasonable for a focused reference database, covering search, specs, maintenance, and part lookup. However, get_model_specs is very broad and partly subsumes get_maintenance, so the set is slightly redundant rather than perfectly scoped.

The surface covers search, model specs with sources, maintenance data, part reverse lookup, and even transaction prices via get_model_specs. Minor gaps like an explicit list-all-models or dedicated price-history tool are workable through search and the broad spec tool.