This is really valuable, especially the 15-25% figure from real production systems — current assumption of 8% is clearly too conservative for agent workloads with tool calling. The cascading retry scenario (retry triggers another tool call that also retries) is a great idea for a worst case column alongside the current realistic estimate. Going to look into this for v2.
That's actually a great direction I haven't thought about — bringing the cost estimate closer to the code rather than keeping it as a separate planning step. The delta view (how much does adding this preprocessing function actually save) would be super useful. Adding it to the v2 roadmap, thanks for this.
If I may add a few comments:
- The idea is awesome, I myself lived in 4 countries (and different regions) within the last 6 years, and such tool would be handy for me.
- As a frequent nomad I look at the economic and social factors rather than climate and culture to which I am flexible. Rainfall and snowfall rates give me no information on climate, however knowing that it rains in Israel only in winter time draws a different picture for me. And Google search gives quite lower numbers on Moscow average humidity 60% vs 76%. Adding Celcius (as you did with cm in rainfall) would be good. I am Euriopean and Forenheit confuse me.
- I think in cities comparison comfort score is the lead "index" but it needs to show the criterias included in this index.
- It would be cool if every city would have a short summary on climate, as it would give much more of an idea of the city comfort.