DutyCite

Each tool targets a distinct step: hts_search finds codes by keyword/prefix, hts_lookup retrieves full rate columns for a known code, and calculate_duty computes the total landed duty stack. The closest overlap is hts_search returning base rates while hts_lookup returns detailed rates, but the descriptions make the intent (discovery vs. detail vs. calculation) clear enough to avoid most misselection.

Two tools use a consistent hts_<verb> prefix pattern, and calculate_duty is a readable verb_noun name. It is a minor deviation (verb-first vs. resource-first) rather than a chaotic mix, so an agent can still infer behavior from names.

Three tools is on the thin side but well-matched to a narrowly scoped duty-calculation service: search, lookup, and calculate are the core operations. Each tool earns its place with no filler, though the surface feels minimal.

The core workflow (find HTS code → look up rates → compute total duty with fees) is fully covered, with free entry points to the paid calculation. The notable gap is product-to-HTS classification guidance, which agents must handle externally before calling these tools.