Concept map: Agents and tool use
Prerequisites (two levels) and direct dependents of Agents and tool use. Show everything
- 3prerequisites shown
- 2direct dependents
- 4lessons use it
Insights 54
- Decompose multi-hop questions instead of hoping one retrieval finds everything
- Route counting and aggregation questions to SQL, not to chunk retrieval
- Give every agent run hard budgets and explicit stopping conditions
- Expose only the tools a task needs, as an explicit allow-list per route
- Prefer narrow, purpose-built tools over generic ones like raw SQL or HTTP
- Make tools ask for missing inputs instead of acting on values the model filled in
- Require human approval for irreversible actions, showing the exact action rather than the model's summary
- Make side-effecting tools idempotent so retries cannot double-act
Projects 9
- Flagship: passenger-rights document Q&A with a retrieval baseline, one controlled improvement and an honest generation mode
- Structured extraction from disruption notices: JSON-schema validation, safe repair and injected-instruction detection
- Tool-calling agent vs deterministic workflow for rebooking proposals after a cancellation
- Prompt-injection red-team harness for a product-Q&A assistant, run on safe fixtures
- Golden-set regression suite that gates prompt changes for a claims-intake triage assistant
- Cost and latency routing study: small model, large model, router and cascade on checkable answers
List view151 concepts
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 11
Day 12
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Day 19
Day 21
Day 22
Day 23
Day 24
Day 25
Day 26
Day 27
Day 28
Day 29
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
Day 49
Day 51
Day 52
Day 53
Day 54
Day 55
Day 58
Day 59
Day 60