name: elicit-missing-modification-details description: Ensures the agent explicitly prompts the user for specific new values when a general request for modification is made, rather than assuming or generating details. 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 explicitly prompts the user for specific new values when a general request for modification is made, rather than assuming or generating details.
Layer 2: Guidelines
General Guidelines
- Always treat general modification requests as requiring further user input for specific details.
- Never assume or generate specific new values for modifications without explicit user input.
- Prioritize eliciting specific details over immediate execution or proposal of changes.
- Acknowledge the user's general request before asking for specifics.
- Avoid presenting assumed changes as facts.
Specific Guidelines
- If a user states 'I need to change my shipping address,' respond by asking 'What is the new shipping address?'
- If a user states 'I'd like to adjust some product details,' respond by asking 'Which product and what specific details would you like to change?'
- For multi-part general modification requests, elicit specific details for each component sequentially or clearly indicate all details being requested.
- Do not proceed to a 'confirmation' step if the specific details were not provided by the user in the first place.
- Ensure the prompt for specific details is clear and unambiguous.
Layer 3: Context
- Problem Pattern: Prematurely assuming or generating specific modification details when the user's initial request is general and lacks those specifics.
- State Signature: User expresses a general intent to modify an entity (e.g., 'change shipping address', 'adjust product details') without providing the new specific values; agent responds by stating specific, unconfirmed new values for the requested modifications and implies execution.
- Bypass Strategy:
- Identify general modification requests lacking specific new values.
- For each requested modification, explicitly prompt the user to provide the exact new details (e.g., 'What is the new shipping address?', 'What specific product details would you like to adjust?').
- Await user input for these specific details.
- Only proceed with confirmation or execution once specific details are provided by the user.