Field Notes: Tool Routing

← Back to the main Geek Mode article

Not every frustrating example fit neatly into a controlled head-to-head test. These are smaller real-world field notes, collected alongside the main comparisons.

“I don’t have access” — then successfully using it anyway

Gemini was asked to use Workspace to search Gmail and Google Drive for files with a particular extension. It replied that it did not have access to Google Workspace, Gmail or Drive, and instructed how to search them manually. A fresh conversation asking it to search just Gmail worked. A follow-up asking it to search Drive also worked. The file being looked for apparently wasn’t there, which isn’t Gemini’s fault — the interesting part is that the product had just successfully used the two integrations it had said it couldn’t access.

The capability exists. The product doesn’t always route the request to it.

Gemini stating it does not have access to Google Workspace, Gmail or Drive
Gemini initially says it can’t access Workspace.
The same Gemini account successfully searching Gmail and Drive after the request was split
The same account then searches Gmail and Drive successfully.

Links that don’t open

Separately, Gemini has successfully located specific Gmail messages but returned links that led to dead pages. The same retrieval job given to ChatGPT produced working message links. This particular anecdote isn’t documented with recovered screenshots and is included here only as a field note, not a fully sourced test.

These are boring failures. That’s precisely why they matter — nobody puts “sometimes gives you a link that doesn’t open” on a benchmark chart, but for daily all-day use, small failures like these determine whether a product saves time or quietly creates more work.

← Previous: 18-page PDF test · Back to the main Geek Mode article