CCTU: Tool Use under Complex Constraints (2026)
Free200-task benchmark across 12 constraint categories (resource, behavior, toolset, response) with step-level validation; no model exceeds 20% completion; models violate constraints in >50% of cases with limited self-correction
About CCTU: Tool Use under Complex Constraints (2026)
CCTU (Complex Constraints for Tool Use) is a benchmark designed to evaluate large language models' ability to use tools while adhering to explicit complex constraints. It introduces a taxonomy of 12 constraint categories across four dimensions: resource, behavior, toolset, and response. The benchmark comprises 200 carefully curated and challenging test cases, each involving an average of seven constraint types and an average prompt length exceeding 4,700 tokens. To enable reliable evaluation, CCTU provides an executable constraint validation module that performs step-level validation during multi-turn interactions between models and their environments. The paper evaluates nine state-of-the-art LLMs in both thinking and non-thinking modes and finds that no model achieves a task completion rate above 20% when strict adherence is required. Models violate constraints in over 50% of cases, particularly in the resource and response dimensions, and demonstrate limited capacity for self-refinement even after receiving detailed feedback. CCTU is released as open-source data and code to facilitate further research.
Key Features
Pros & Cons
- Comprehensive taxonomy covering multiple constraint dimensions
- Executable validation ensures reliable and objective evaluation
- Challenging tasks that expose limitations of current LLMs
- Open-source and freely available for reproducibility
- Step-level validation allows detailed error analysis
- No current model achieves above 20% task completion under strict constraints
- Models violate constraints in over 50% of cases, especially in resource and response dimensions
- Limited self-refinement even with detailed feedback on violations
- Average prompt length over 4,700 tokens may be computationally expensive
- Only 200 test cases, potentially limited coverage of real-world scenarios