Your track_shipment(tracking_id) tool queries an external logistics API that sometimes fails - the API may be temporarily unavailable, the tracking ID may be malformed, or the shipment may not exist. Currently, your tool raises a Python exception when errors occur. Users report the agent gives unhelpful responses like "I'm having trouble with that request" instead of suggesting alternatives such as verifying the tracking number format or checking by order number. How should you handle errors in tool results?

• A. Return structured error information as normal tool output including error type, recoverability status, and actionable context for the user.
• B. 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.
• C. 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.
• D. 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.

You are building a structured data extraction system using Claude. The system extracts information from unstructured documents, validates the output using JSON schemas, and maintains high accuracy. It must handle edge cases gracefully and integrate with downstream systems.
Your extraction pipeline occasionally receives responses that cannot be parsed as valid JSON, causing downstream processing failures. The current implementation prompts Claude to return JSON in the response text and then parses it.
What is the most reliable approach to ensure Claude returns valid, schema-compliant structured data?

• A. Add explicit formatting instructions to the prompt with JSON examples, emphasizing that Claude must return only valid JSON with no surrounding text.
• B. Implement a retry loop that catches JSON parsing errors and re-prompts Claude with the error details, asking it to correct the malformed output.
• C. Use regular expressions to locate and extract JSON from the response text, handling cases where Claude includes explanatory text around the JSON block.
• D. Define a tool with a JSON schema specifying the expected structure, using tool use to constrain Claude's output to schema-compliant JSON.

You are building a structured data extraction system using Claude. The system extracts information from unstructured documents, validates the output using JavaScript Object Notation (JSON) schemas, and maintains high accuracy. It must handle edge cases gracefully and integrate with downstream systems.
Your system has been running for 3 weeks and human reviewers have corrected 847 extractions.
Analysis reveals a recurring pattern: when recipes use informal measurements like "a handful" or
"a splash," the model either invents specific amounts or leaves fields empty--accounting for 23% of all corrections.
How should you use this feedback to improve extraction accuracy?

• A. Add few-shot examples to your prompt demonstrating correct handling of informal measurements--extracting them verbatim rather than converting or omitting them.
• B. Implement a post-processing layer that uses pattern matching to detect informal measurement phrases in source text and automatically populate values when the extraction is empty.
• C. Fine-tune the model on the 847 corrected extractions.
• D. Update your JSON schema to add a "measurement_type" enum field (precise/informal).

Your get_portfolio_value tool returns the total value of a user's investment portfolio. You're deciding between returning a structured JSON object with explicit fields versus returning the information as a formatted text string. What is the primary advantage of using structured output with defined fields?

• A. Structured JSON is processed deterministically by the model, significantly improving accuracy when extracting values.
• B. The agent can reliably extract specific values without parsing free-form text, reducing errors in subsequent operations.
• C. JSON schemas automatically validate that the underlying API returned correct data before the agent processes it.
• D. Structured JSON consumes significantly fewer tokens than natural language, substantially reducing API costs.

Your pipeline reviews approximately 200 database-migration scripts daily using the Message Batches API. Each request includes a shared 8,000-token system prompt containing migration- review guidelines and schema documentation, followed by an individual migration script. You added cache_control breakpoints to the shared system prompt in every request, but monitoring shows cache-hit rates of only 32%, with misses concentrated among requests processed later in the batch window. Which change addresses the root cause without adding sequential-processing latency?

• A. Move the cache_control breakpoint from the shared system prompt to each migration script so similar code patterns can be reused.
• B. Configure the cache breakpoints to use the extended one-hour TTL instead of the default five- minute TTL.
• C. Add cache-prewarming requests with max_tokens: 0 at the beginning of every batch.
• D. Split the 200 requests into ten sequential batches of 20, submitting each batch only after the previous batch completes.