← All speakers

Bio, Work & Ideas

Sohail Shaikh

Conference affiliation: Prosodica · 2026

Sohail Shaikh is a data scientist specializing in applied AI, natural language processing, conversational intelligence, and retrieval-augmented generation. His work addresses a practical problem in agent design: loading every available tool into every request makes models slower, costlier, and more likely to choose incorrectly.

His technical background spans engineering, analytics, and experimentation. Public projects include A/B testing, a SQL car-rental database, customer-lifetime-value analysis, and odsc-lancedb.

At AI Engineer World’s Fair 2026, Shaikh represented Prosodica alongside Ankush Rastogi in a session on scalable agent tooling. Their central ideas include:

  • Semantic routing as RAG for tools: Embed and index tool descriptions, match each request against that index, and provide the model only the most relevant schemas.
  • Just-in-time context injection: Load capabilities after understanding the request, keeping the active context compact even as the overall tool catalog expands.
  • Production-minded agent evaluation: Measure tool-selection accuracy, first-token latency, and token costs together; address retrieval misses through stronger descriptions, adjusted retrieval limits, and fallback searches.

Shaikh favors proportionate implementation: smaller toolsets can remain statically loaded, while larger catalogs benefit from retrieval infrastructure that limits irrelevant choices.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Semantic routing and just-in-time context let an agent’s tool catalog grow without forcing the model to consider every schema on every request.

  • When every request carries every tool
    0:01 ↗
  • A larger choice set can make selection worse
    4:15 ↗
  • Paying to describe tools the request will never use
    5:45 ↗
  • Retrieve tools, then load their schemas
    9:19 ↗
  • Measure the working set, not just the catalog
    12:47 ↗
  • Make the retrieved schemas the model’s actual tool list
    15:54 ↗
  • A flight request and a weather request get different tools
    18:56 ↗
  • Connect retrieval to evaluation and maintenance
    20:22 ↗
  • Use the existing retrieval ecosystem
    22:00 ↗
  • Recover from misses without rebuilding the trap
    24:27 ↗

References