The requirement to pull datasheets is kind of a deal-breaker. My current project has 70 BOM line items. I'm not shoving 70 datasheets into your tool, sorry.
As a reference for the OP I did a public professional-informal-mini-design-review over here a while ago: https://news.ycombinator.com/item?id=44651770 . I didn't pull any of those datasheets because I didn't need to. It would be interesting to see what your tool says about that design, and compare it to the types of things I thought needed attention.
Agreed. Tooling like this also needs far more careful structuring of the inputs than a thin wrapper like this.
It burnt a bunch of tokens and filled the context reading all datasheet files, whereas documentation should be queried to answer specific details connected to relevant netlist/sch nodes.