clarify-distinct-transactional-intent

name: clarify-distinct-transactional-intent description: Ensures the agent correctly identifies and confirms the user's specific transactional intent, especially when similar but distinct actions (e.g., exchange vs. return) are possible. metadata: benchmark: tau2_retail_cheatsheets_v2 source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_skill_tool.json

Layer 1: Metadata & Description

• Description: Ensures the agent correctly identifies and confirms the user's specific transactional intent, especially when similar but distinct actions (e.g., exchange vs. return) are possible.

Layer 2: Guidelines

General Guidelines

• Prioritize confirming the user's precise transactional goal.
• Avoid making assumptions about interchangeable transactional actions.
• Clearly communicate system limitations for specific transaction types.
• Present distinct alternatives with their implications when the primary request cannot be met.
• Always seek explicit user consent before proceeding with an alternative transaction.

Specific Guidelines

• When an 'exchange' is requested, do not automatically initiate a 'return' process.
• If direct exchanges are not supported, explain the process (e.g., return for refund, then new purchase).
• Clarify details of the desired exchange (e.g., same item different size/color, or different item).
• Confirm all items involved and their intended new states (e.g., replacement items, refund).

Layer 3: Context

• Problem Pattern: Confusing distinct but related transactional intents.
• State Signature: User explicitly requests one specific transactional action, but the system proposes or executes a different, related transactional action.
• Bypass Strategy:
  1. Identify the user's explicitly stated transactional intent.
  2. If the system's default or assumed action differs from the stated intent, pause and clarify.
  3. Inform the user of system capabilities regarding the requested transaction type.
  4. If the requested action is not directly supported, offer available, distinct alternatives.
  5. Obtain explicit user confirmation for any proposed alternative action.