Your process_refund tool returns two types of errors: technical errors ("503 Service Unavailable",
"Connection timeout") that are transient (5% of calls), and business errors ("Order exceeds
30 day return window", "Item already refunded") that are permanent (12% of calls). Monitoring shows the agent wastes 3-4 turns retrying business errors that can never succeed. Currently, both error types return only a plain text message to Claude. What's the most effective way to reduce wasted retries while improving customer-facing response quality?

• A. Add few-shot examples showing how to distinguish retriable from non-retriable errors by parsing error message text.
• B. Implement automatic retry logic at the tool level for technical errors only, passing business errors to Claude without retries.
• C. Add a check_refund_eligibility tool that must be called before process_refund to prevent business rule violations.
• D. Return structured error responses with retriable: false for business errors and a customer-friendly explanation for Claude to use.

A developer includes multiple unrelated tasks inside one extremely long prompt. What is the MOST likely outcome?

• A. Faster inference.
• B. Increased prompt clarity.
• C. Reduced instruction clarity.
• D. Improved reasoning.

Your post_content tool requires user confirmation before publishing. The current workflow displays "Ready to post to social media. Confirm?" and analytics show users approve 98% of requests within 2 seconds. Post-mortems reveal incidents where posts went to wrong accounts, were scheduled for wrong times, or contained errors - all confirmed by users without catching the mistakes. How should you redesign the confirmation workflow?

• A. Include the complete post text, target account, scheduled time, and platform in the confirmation request
• B. Add a mandatory waiting period before the confirm option becomes available
• C. Auto-approve routine posts and only require explicit confirmation for unusual patterns like posting to new accounts or large audiences
• D. Require users to type a confirmation phrase instead of clicking a button

You're implementing the escalation logic for when the agent should call escalate_to_human. Your team proposes four different approaches for triggering escalation. Which approach will most reliably identify cases that genuinely require human intervention?

• A. Implement sentiment analysis that monitors for frustration indicators (negative language, repeated questions, exclamation marks) and trigger escalation when the frustration score exceeds a configured threshold.
• B. Instruct the agent to escalate when the customer requests a human, when the issue requires policy exceptions, or when the agent cannot make meaningful progress.
• C. Build a rules engine that maps specific issue types, customer segments, and product categories to escalation decisions, removing the need for model judgment calls.
• D. Configure the agent to escalate after three consecutive tool calls that fail to resolve the customer's stated issue, ensuring a reasonable attempt before involving a human.

A legal department requires Claude to answer only when sufficient evidence exists in retrieved documents. What should Claude do if evidence is insufficient?

• A. Increase creativity.
• B. Search social media automatically.
• C. Invent a likely answer.
• D. Clearly indicate insufficient information.