confirm-transaction-scope

name: confirm-transaction-scope description: Prevents the agent from assuming the full scope of a general transactional request without explicit user confirmation of specific items or entities. metadata: benchmark: tau2_retail_cheatsheets_v2 source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_skill_tool.json

Layer 1: Metadata & Description

• Description: Prevents the agent from assuming the full scope of a general transactional request without explicit user confirmation of specific items or entities.

Layer 2: Guidelines

General Guidelines

• Always clarify the scope of general transactional requests before proceeding with any action.
• Do not assume 'all' when the user's language is general or ambiguous (e.g., 'some things').
• List all potential items or entities clearly for the user to review and select from.
• Prioritize explicit user confirmation of scope over inferred intent.
• Avoid pre-emptively processing any items or entities until the exact scope is confirmed.

Specific Guidelines

• When a user makes a general request like 'I want to return some things,' identify all eligible items across all relevant orders.
• Present a clear, itemized list of all eligible items and their associated orders to the user.
• Ask a clarifying question such as, 'Which of these items would you like to include in the transaction?' or 'Are you looking to act on all identified items, or just specific ones?'
• Wait for explicit user selection or confirmation of the specific items or entities for the transaction.
• If the user confirms 'all,' then proceed with processing all identified items; otherwise, proceed only with the specified items.

Layer 3: Context

• Problem Pattern: Assuming the full scope of a general transactional request without explicit user confirmation.
• State Signature: User initiates a general transactional request, and the agent identifies multiple potential items or entities for the action, then proceeds to act on all of them without confirming the user's specific intent regarding scope.
• Bypass Strategy:
  1. Identify all potential items or entities related to the general request.
  2. Present the identified items or entities to the user for review.
  3. Explicitly ask the user to confirm which specific items or entities they wish to include in the transaction.
  4. Proceed only with the items or entities explicitly confirmed by the user.