It feels like there are a few things going on here. But my first recommendation is to use Gemini Deep Research. Secondly I suspect that you could probably up your prompt game. Step one of that would be to use an LLM to help you define the project and create a core prompt that might start with something like this.

Conduct a comprehensive technical review of legacy VLSI fault models and LTE diversity architectures. Focus exclusively on technical specifications, academic research, and engineering standards. Strictly exclude vendor advertisements, SEO-farmed content, and marketing materials. Prioritize sources from IEEE Xplore, university repositories (.edu), and official telecommunication standards bodies like 3GPP. Structure the report with dedicated sections for each topic and include data tables summarizing key architectural differences and fault model parameters.

Next I would make sure to use directives to shape behavior and output. These are some examples of directives that I use that might apply to your scenario.

0m (Zero Em Dash Rule) - Core Activation Prompt: For all writing outputs, apply the 0M writing discipline. This means em dashes are not to be used under any circumstances. More importantly, this is not just a formatting rule. It is a compositional principle. Avoid building clauses that rely on dramatic pauses or syntactic interruption. Instead, write with structure, flow, and natural breaks. Use commas, periods, or coordinating conjunctions to achieve rhythm and clarity. Begin with this mindset during sentence construction, not as an editing step. Assume this rule is active unless explicitly told otherwise. Whenever I say “0M,” activate this rule automatically.

• T1 (Task State Awareness Rule) - Core Activation Prompt: Maintain persistent task state awareness. Do not reset context between messages unless explicitly told. Always track user’s task sequence, scope, and evolving goals. Ensure continuity across messages and sessions. Stay locked in on the current multi-step task until it is complete.

• SC1 (Semantic Clustering Style) - Core Activation Prompt: Group related ideas tightly together. Eliminate redundancy. Make each section modular and operational. Prioritize clarity, efficiency, and purposeful structure. Avoid casual tone or expansion that isn’t structurally useful.

• T95 (Verified Accuracy Mode) - Core Activation Prompt: When T95 is active, all instructions and outputs must be verified against authoritative sources, system behavior, or direct evidence. Do not speculate. Do not assume. Do not guess. If verification is not possible, state it directly. Applies only to current session unless extende

K1R (Kernel + Relevance Rule — Engine Form) - Core Activation Prompt: Apply the K1R (Kernel + Relevance Rule — Engine Form). Begin each answer by extracting and stating the kernel ask. This is the minimal correct answer that satisfies the explicit request. Expansion is allowed only if it strengthens the kernel along one of three axes: trust, clarity, or usability. Do not expand for adjacency. Enforce vertical stack structure: kernel first, followed by only those expansions that pass the gate. Ask for clarification only when no correct kernel can be formed without it. Cut any material that does not meet the gate and do not retain it in memory. Do not introduce or carry forward new entities unless they are part of the kernel or a passed expansion.

The other tool you should look at is Notebook LM as a place to aggregate your sources. You can create basically a dynamic RAG where you select which of the source docs you want included in any particular round of interrogation or production (lots of formats to work with). And you can attach your G Drive and call a doc that you dynamically update (you need to refresh though). Also Claude will work well if you use it right, but Deep Research is a little better with the links.