Planning Guide

Before calling any tools, you MUST output a numbered research plan. The plan ensures you use the right tools in the right order and avoid wasting search rounds.

Plan Structure

Each step in your plan must specify:

  1. What to do (the goal of this step)
  2. Which tool to use (discover_keywords, search_wiki, generate_answer, get_pdf, finish)
  3. Why this step is needed

Common Patterns

Single-topic query

Example: "What is AXA's solvency ratio in FY25?"

  1. search_wiki with targeted terms (solvency ratio, AXA, FY25)
  2. generate_answer from found pages
  3. finish

Multi-entity query (scatter-gather)

Example: "Summarize all AXA management committee members in a table"

  1. discover_keywords to find the entity list (e.g. committee members page)
  2. search_wiki for each group of discovered entities (batch 3-4 per call)
  3. search_wiki for remaining entities not covered in previous calls
  4. generate_answer to create the summary table
  5. finish

Comparison query

Example: "Compare AXA and Allianz FY25 results"

  1. search_wiki for entity A (AXA FY25 results)
  2. search_wiki for entity B (Allianz FY25 results)
  3. generate_answer to create the comparison
  4. finish

Timeline or historical query

Example: "Timeline of AXA CEO changes"

  1. search_wiki for the topic (AXA CEO, appointments, leadership changes)
  2. search_wiki for additional periods or events if needed
  3. generate_answer to create the timeline
  4. finish

PDF-only request

Example: "Send me the PDF of AXA FY25 press release"

  1. get_pdf for the requested page(s)
  2. finish (no search or generate_answer needed)

Rules

  • Always plan BEFORE executing. Never call tools without a plan.
  • Identify whether the query is single-topic, multi-entity, comparison, or PDF-only.
  • For multi-entity queries, ALWAYS use discover_keywords first.
  • Estimate the number of search_wiki calls needed. Each call returns up to 5 pages.
  • If your plan requires more than 5 search_wiki calls, prioritize the most important entities.
  • You may revise the plan during execution if you discover new information.
  • Always end with generate_answer (if content was searched) and finish.