The community member is experiencing issues with their RouterQueryEngine, where many prompts are unnecessarily going to the SqlAgent rather than the vectorAgent. They have tried changing the description, which has helped, but there are still a few prompts that go to the SqlAgent. The comments suggest that better describing the two tools and trying few-shot learning may help improve the routing mechanism at the LLLM routing layer.
I have my RouterQueryEngine configured for sql and vector agent, there are many false positives of the prompt unnecesarily to going to the SqlAgent rather than vectorAgent, is there any way to improve the routing mechanism at the LLLM routing layer ? I changed the description and it made a really good progress, but still there are few that goes to the sqlAgent
