Option D addresses the observed inconsistency at the model-behavior level. A schema can require that materials be a string, but it cannot teach Claude which lexical form the application considers canonical or demonstrate when a source phrase should populate the field. Anthropic identifies examples as one of the most reliable ways to steer output format, structure, and consistency, recommending several relevant and diverse examples that mirror the real task in its prompting best practices . Complete input-output pairs show both recognition and normalization: for example, a description containing "60% cotton, 40% polyester" can consistently map to the chosen "cotton/polyester blend" representation. They can also include difficult cases where material information is embedded indirectly in prose. Temperature zero reduces sampling variability but does not repair an underspecified transformation rule. A more capable model likewise lacks the missing formatting convention. Making the field required is dangerous because documents may legitimately omit materials; it can force unsupported values and increase hallucinations. Few-shot examples therefore supply the missing decision boundary while preserving truthful absence handling. The examples should be evaluated on held-out descriptions and supplemented by deterministic post-processing if downstream systems require an exact controlled vocabulary.

Option C avoids an unnecessary agent boundary. The coordinator already possesses the accumulated findings and can perform a straightforward summary without serializing, transferring, and reprocessing more than
80,000 tokens in another context window. Subagents should be reserved for work that requires isolated context, specialized instructions, separate tools, or an independent analytical process.
Anthropic's current prompting guidance advises using subagents for independent workstreams and parallel or context-isolated tasks, while handling simpler tasks directly. Anthropic also notes that excessive subagent use creates unnecessary cost and latency.
Option A generates multiple summaries speculatively, consuming resources even if they are never requested and creating cache-invalidation complexity whenever findings change. Option B may reduce repeated input- token cost, but it does not eliminate subagent startup, message processing, or the unnecessary orchestration round trip. Option D introduces an iterative request protocol that will likely increase latency further. Direct coordinator summarization uses information already available in active context and therefore provides the smallest architectural change, lowest token-transfer overhead, and fastest response while preserving subagent synthesis for genuinely complex comparative or cross-source analysis.

In the standard Claude tool-use loop, the application executes lookup_order and sends its output back as a tool_result . That result becomes part of the conversation state available to Claude. Claude then evaluates the purchase date, refund policy, customer request, authorization constraints, and available tools before selecting the next action.
Anthropic describes client-tool orchestration as a repeated loop: Claude emits a tool_use request, the application executes it, returns a tool_result , and Claude continues reasoning from the updated conversation.
Claude, rather than the tool implementation, selects when and how to invoke the next available tool unless the application has explicitly implemented a fixed workflow. ( https://platform.claude.com/docs/en/agents-and- tools/tool-use/how-tool-use-works ) Options B and C describe possible custom orchestration architectures, but neither is stated in the scenario.
Option D is inconsistent with adaptive agent behavior because later actions depend on information that did not exist before lookup_order completed. A rigid sequence would not respond appropriately to different purchase dates, eligibility states, or order conditions.
The tool result should return high-signal fields such as purchase date, return-window status, refund eligibility, existing refund status, and stable order identifiers so Claude can make the subsequent decision accurately.
Official references/topics: Tool-result continuation, adaptive agent loops, model-directed tool selection, sequential dependency handling.

The agent must preserve durable state for several concurrently open issues without keeping every conversational turn in the active context window. Option D creates a structured issue ledger containing identifiers, issue type, requested action, current status, completed steps, unresolved questions, and relevant tool outputs.
Anthropic recommends structured note-taking for long-horizon agents. In this pattern, critical state is written outside the context window and retrieved later, allowing the agent to preserve dependencies and progress across dozens of tool calls. Anthropic also describes compaction as retaining critical details while discarding redundant raw messages and historical tool output. ( https://www.anthropic.com/engineering/effective-context- engineering-for-ai-agents ) Option A is better than retaining the entire transcript, but a narrative summary can merge separate issues or obscure exact identifiers and statuses. Option B will discard the refund conversation because it occurred outside the most recent 30 turns. Option C may recover current backend facts, but it cannot reconstruct conversational commitments, prior explanations, or why a particular action remains pending.
A structured context layer should maintain one record per issue and be updated after every material action.
The active prompt can include compact summaries of all open issues and expanded details only for the issue currently being discussed.
Official references/topics: Structured note-taking, external agent memory, context compaction, multi-issue state management.