A. Have the report generator query the web search agent to re-locate sources for claims in the final report.

B. Instruct the synthesis agent to embed source references inline within its summary text using a consistent citation format.

C. Skip summarization and pass full raw outputs from web search and document analysis directly to the report generator.

D. Have each agent output structured data separating content summaries from source metadata (URLs, document names, page numbers).

A. Return a generic error response (e.g., {"success": false, "error": "lookup_failed"}) for all failure cases to maintain a consistent schema and avoid exposing internal error details.

B. Implement retry logic with exponential backoff inside the tool implementation so transient errors are automatically handled and only return a result after all retry attempts are exhausted.

C. Return structured error information as normal tool output including error type, recoverability status, and actionable context for the user.

D. Create dedicated error-recovery tools (retry_tracking_lookup, search_by_order_number) that the model can invoke after the primary tracking tool returns a failure indicator.

A. Return the error message in the tool result content with the isError flag set to true

B. Return a success response with a "status" field indicating the error type

C. Throw an exception from the tool handler so the agent framework can catch and log it

D. Log the error server-side and return an empty result to avoid confusing the model

A. Raise temperature.

B. Remove role instructions.

C. Shorten all outputs.

D. Add reliable retrieval sources.

A. Resume the analysis session with fork_session enabled, creating a separate branch for each testing strategy.

B. Export the analysis session's key findings to a file, then create two new sessions that reference this file.

C. Continue in the original session, developing end-to-end tests first, then snapshot tests sequentially.

D. Start two fresh sessions, having each re-read the relevant source files before beginning.

A. Use /clear to reset context completely, then start fresh with physics exploration using file paths from the project's CLAUDE.md.

B. Spawn a sub-agent to explore physics independently, then manually synthesize its findings with the rendering knowledge accumulated in the main conversation.

C. Continue in the current context with more targeted prompts referencing the specific classes by name.

D. Summarize key rendering findings, then spawn a sub-agent for physics exploration with that summary in its initial context.

A. Read the project's README and service configuration files to understand the architecture, then systematically Read source files in each service directory.

B. Use Glob to find files in directories commonly associated with error handling (such as errors/, exceptions/,or handlers/) across all services, then Read each matching file.

C. Use Grep to find all files that import the project's error handling module, then Read those files to locate custom error definitions.

D. Use Grep to search for distinctive text from the error message (like "SYNC_CONFLICT" or "entity version mismatch"), then Read the matching files to understand context.