id stringlengths 8 8 | category stringclasses 8
values | difficulty stringclasses 3
values | input stringlengths 103 659 | context nulllengths 3 5 ⌀ | expected_behavior stringlengths 137 314 | failure_modes listlengths 3 5 | fix_signal stringlengths 92 159 |
|---|---|---|---|---|---|---|---|
TOOL-001 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for my manager",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for my manager scenarios. |
TOOL-002 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email nora@example.com with subject "Confirmed" an... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a client",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a client scenarios. |
TOOL-003 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Denver for 2026-06... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for our support team",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for our support team scenarios. |
TOOL-004 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to review the pull request by end of month, prior... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a new teammate",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a new teammate scenarios. |
TOOL-005 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (15 * 7) - 5, then report the number. I need this for my teacher before our morning ... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for my teacher",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for my teacher scenarios. |
TOOL-006 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Owen from design and return up to 3 matches. I need this for the project lead befor... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for the project lead",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for the project lead scenarios. |
TOOL-007 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my downloads folder for a file about proposal with extension xlsx. I need... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a vendor",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a vendor scenarios. |
TOOL-008 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for my roommate",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for my roommate scenarios. |
TOOL-009 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a school admin",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a school admin scenarios. |
TOOL-010 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email jon@example.com with subject "Schedule" and ... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for the operations channel",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for the operations channel scenarios. |
TOOL-011 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Tampa for July 4 i... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a product review",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a product review scenarios. |
TOOL-012 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to pay rent by tonight, priority high. I need thi... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a family group chat",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a family group chat scenarios. |
TOOL-013 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (23 * 8) - 0, then report the number. I need this for a lab partner before our morni... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a lab partner",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a lab partner scenarios. |
TOOL-014 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Nora from the clinic and return up to 3 matches. I need this for the help desk befo... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for the help desk",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for the help desk scenarios. |
TOOL-015 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my projects folder for a file about receipt with extension docx. I need t... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a hiring panel",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a hiring panel scenarios. |
TOOL-016 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for the finance folder",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for the finance folder scenarios. |
TOOL-017 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a workshop handout",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a workshop handout scenarios. |
TOOL-018 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email owen@example.com with subject "Update" and s... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for the shift lead",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for the shift lead scenarios. |
TOOL-019 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Phoenix for June 1... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a release note",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a release note scenarios. |
TOOL-020 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to call the clinic by 2026-06-08, priority low. I... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a volunteer coordinator",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a volunteer coordinator scenarios. |
TOOL-021 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (31 * 2) - 8, then report the number. I need this for a parent email before our morn... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a parent email",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a parent email scenarios. |
TOOL-022 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Jon from Northwind and return up to 3 matches. I need this for a design critique be... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for a design critique",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for a design critique scenarios. |
TOOL-023 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my shared folder for a file about dataset with extension txt. I need this... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for the travel group",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for the travel group scenarios. |
TOOL-024 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for a security review",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for a security review scenarios. |
TOOL-025 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a weekly recap",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a weekly recap scenarios. |
TOOL-026 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email nora@example.com with subject "Confirmed" an... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a tenant message",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a tenant message scenarios. |
TOOL-027 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Denver for 2026-06... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for an onboarding doc",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for an onboarding doc scenarios. |
TOOL-028 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to review the pull request by end of month, prior... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a clinic note",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a clinic note scenarios. |
TOOL-029 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (39 * 3) - 3, then report the number. I need this for a board update before our morn... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a board update",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a board update scenarios. |
TOOL-030 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Owen from design and return up to 3 matches. I need this for a class handout before... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for a class handout",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for a class handout scenarios. |
TOOL-031 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my downloads folder for a file about proposal with extension xlsx. I need... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a contractor reply",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a contractor reply scenarios. |
TOOL-032 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for an incident log",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for an incident log scenarios. |
TOOL-033 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a planning memo",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a planning memo scenarios. |
TOOL-034 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email jon@example.com with subject "Schedule" and ... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a training exercise",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a training exercise scenarios. |
TOOL-035 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Tampa for July 4 i... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a grant draft",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a grant draft scenarios. |
TOOL-036 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to pay rent by tonight, priority high. I need thi... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a team retrospective",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a team retrospective scenarios. |
TOOL-037 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (47 * 4) - 11, then report the number. I need this for a user interview before our m... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a user interview",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a user interview scenarios. |
TOOL-038 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Nora from the clinic and return up to 3 matches. I need this for a sales follow-up ... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for a sales follow-up",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for a sales follow-up scenarios. |
TOOL-039 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my projects folder for a file about receipt with extension docx. I need t... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a maintenance ticket",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a maintenance ticket scenarios. |
TOOL-040 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for a study session",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for a study session scenarios. |
TOOL-041 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for my manager",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for my manager scenarios. |
TOOL-042 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email owen@example.com with subject "Update" and s... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a client",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a client scenarios. |
TOOL-043 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Phoenix for June 1... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for our support team",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for our support team scenarios. |
TOOL-044 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to call the clinic by 2026-06-08, priority low. I... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a new teammate",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a new teammate scenarios. |
TOOL-045 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (55 * 5) - 6, then report the number. I need this for my teacher after yesterday?s d... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for my teacher",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for my teacher scenarios. |
TOOL-046 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Jon from Northwind and return up to 3 matches. I need this for the project lead aft... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for the project lead",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for the project lead scenarios. |
TOOL-047 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my shared folder for a file about dataset with extension txt. I need this... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a vendor",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a vendor scenarios. |
TOOL-048 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for my roommate",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for my roommate scenarios. |
TOOL-049 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a school admin",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a school admin scenarios. |
TOOL-050 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email nora@example.com with subject "Confirmed" an... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for the operations channel",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for the operations channel scenarios. |
TOOL-051 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Denver for 2026-06... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a product review",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a product review scenarios. |
TOOL-052 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to review the pull request by end of month, prior... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a family group chat",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a family group chat scenarios. |
TOOL-053 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (63 * 6) - 1, then report the number. I need this for a lab partner after yesterday?... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a lab partner",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a lab partner scenarios. |
TOOL-054 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Owen from design and return up to 3 matches. I need this for the help desk after ye... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for the help desk",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for the help desk scenarios. |
TOOL-055 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my downloads folder for a file about proposal with extension xlsx. I need... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a hiring panel",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a hiring panel scenarios. |
TOOL-056 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for the finance folder",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for the finance folder scenarios. |
TOOL-057 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a workshop handout",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a workshop handout scenarios. |
TOOL-058 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email jon@example.com with subject "Schedule" and ... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for the shift lead",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for the shift lead scenarios. |
TOOL-059 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Tampa for July 4 i... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a release note",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a release note scenarios. |
TOOL-060 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to pay rent by tonight, priority high. I need thi... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a volunteer coordinator",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a volunteer coordinator scenarios. |
TOOL-061 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (71 * 7) - 9, then report the number. I need this for a parent email after yesterday... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a parent email",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a parent email scenarios. |
TOOL-062 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Nora from the clinic and return up to 3 matches. I need this for a design critique ... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for a design critique",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for a design critique scenarios. |
TOOL-063 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my projects folder for a file about receipt with extension docx. I need t... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for the travel group",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for the travel group scenarios. |
TOOL-064 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for a security review",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for a security review scenarios. |
TOOL-065 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a weekly recap",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a weekly recap scenarios. |
TOOL-066 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email owen@example.com with subject "Update" and s... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a tenant message",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a tenant message scenarios. |
TOOL-067 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Phoenix for June 1... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for an onboarding doc",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for an onboarding doc scenarios. |
TOOL-068 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to call the clinic by 2026-06-08, priority low. I... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a clinic note",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a clinic note scenarios. |
TOOL-069 | Tool Calling | easy | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (79 * 8) - 4, then report the number. I need this for a board update after yesterday... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a board update",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a board update scenarios. |
TOOL-070 | Tool Calling | easy | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Jon from Northwind and return up to 3 matches. I need this for a class handout afte... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for a class handout",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for a class handout scenarios. |
TOOL-071 | Tool Calling | easy | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my shared folder for a file about dataset with extension txt. I need this... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a contractor reply",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a contractor reply scenarios. |
TOOL-072 | Tool Calling | easy | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for an incident log",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for an incident log scenarios. |
TOOL-073 | Tool Calling | easy | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a planning memo",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a planning memo scenarios. |
TOOL-074 | Tool Calling | easy | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email nora@example.com with subject "Confirmed" an... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a training exercise",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a training exercise scenarios. |
TOOL-075 | Tool Calling | easy | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Denver for 2026-06... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a grant draft",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a grant draft scenarios. |
TOOL-076 | Tool Calling | easy | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to review the pull request by end of month, prior... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a team retrospective",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a team retrospective scenarios. |
TOOL-077 | Tool Calling | medium | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (87 * 2) - 12, then report the number. Optional details can be left blank; do not bl... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a user interview",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a user interview scenarios. |
TOOL-078 | Tool Calling | medium | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Owen from design and return up to 3 matches. Optional details can be left blank; do... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for a sales follow-up",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for a sales follow-up scenarios. |
TOOL-079 | Tool Calling | medium | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my downloads folder for a file about proposal with extension xlsx. Option... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a maintenance ticket",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a maintenance ticket scenarios. |
TOOL-080 | Tool Calling | medium | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for a study session",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for a study session scenarios. |
TOOL-081 | Tool Calling | medium | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for my manager",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for my manager scenarios. |
TOOL-082 | Tool Calling | medium | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email jon@example.com with subject "Schedule" and ... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for a client",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for a client scenarios. |
TOOL-083 | Tool Calling | medium | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Tampa for July 4 i... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for our support team",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for our support team scenarios. |
TOOL-084 | Tool Calling | medium | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to pay rent by tonight, priority high. Optional d... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a new teammate",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a new teammate scenarios. |
TOOL-085 | Tool Calling | medium | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (95 * 3) - 7, then report the number. Optional details can be left blank; do not blo... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for my teacher",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for my teacher scenarios. |
TOOL-086 | Tool Calling | medium | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Nora from the clinic and return up to 3 matches. Optional details can be left blank... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for the project lead",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for the project lead scenarios. |
TOOL-087 | Tool Calling | medium | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my projects folder for a file about receipt with extension docx. Optional... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a vendor",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a vendor scenarios. |
TOOL-088 | Tool Calling | medium | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for my roommate",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for my roommate scenarios. |
TOOL-089 | Tool Calling | medium | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a school admin",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a school admin scenarios. |
TOOL-090 | Tool Calling | medium | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email owen@example.com with subject "Update" and s... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for the operations channel",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for the operations channel scenarios. |
TOOL-091 | Tool Calling | medium | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Phoenix for June 1... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a product review",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a product review scenarios. |
TOOL-092 | Tool Calling | medium | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to call the clinic by 2026-06-08, priority low. O... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a family group chat",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a family group chat scenarios. |
TOOL-093 | Tool Calling | medium | Available tool schema: {"name":"calculator.calculate","description":"Calculate an expression.","parameters":{"type":"object","properties":{"expression":{"type":"string"}},"required":["expression"]}}
User request: Use the calculator for (103 * 4) - 2, then report the number. Optional details can be left blank; do not bl... | null | Call calculator.calculate with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calculator.calculate when the schema is provided for a lab partner",
"omits a required field for calculator.calculate",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calculator.calculate calls with realistic optional-detail noise for a lab partner scenarios. |
TOOL-094 | Tool Calling | medium | Available tool schema: {"name":"contacts.search","description":"Search contacts.","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}}
User request: Find my contact for Jon from Northwind and return up to 3 matches. Optional details can be left blank; ... | null | Call contacts.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call contacts.search when the schema is provided for the help desk",
"omits a required field for contacts.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for contacts.search calls with realistic optional-detail noise for the help desk scenarios. |
TOOL-095 | Tool Calling | medium | Available tool schema: {"name":"file.search","description":"Search files.","parameters":{"type":"object","properties":{"query":{"type":"string"},"extension":{"type":"string"},"folder":{"type":"string"}},"required":["query"]}}
User request: Search my shared folder for a file about dataset with extension txt. Optional de... | null | Call file.search with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call file.search when the schema is provided for a hiring panel",
"omits a required field for file.search",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for file.search calls with realistic optional-detail noise for a hiring panel scenarios. |
TOOL-096 | Tool Calling | medium | Available tool schema: {"name":"ticket.create","description":"Create support ticket.","parameters":{"type":"object","properties":{"summary":{"type":"string"},"severity":{"type":"string","enum":["low","medium","high","critical"]},"description":{"type":"string"}},"required":["summary","severity"]}}
User request: Create a... | null | Call ticket.create with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call ticket.create when the schema is provided for the finance folder",
"omits a required field for ticket.create",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for ticket.create calls with realistic optional-detail noise for the finance folder scenarios. |
TOOL-097 | Tool Calling | medium | Available tool schema: {"name":"calendar.create_event","description":"Create a calendar event.","parameters":{"type":"object","properties":{"title":{"type":"string"},"date":{"type":"string"},"time":{"type":"string"},"duration_minutes":{"type":"integer"},"notes":{"type":"string"}},"required":["title","date","time"]}}
Us... | null | Call calendar.create_event with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call calendar.create_event when the schema is provided for a workshop handout",
"omits a required field for calendar.create_event",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for calendar.create_event calls with realistic optional-detail noise for a workshop handout scenarios. |
TOOL-098 | Tool Calling | medium | Available tool schema: {"name":"email.send","description":"Send an email.","parameters":{"type":"object","properties":{"to":{"type":"string"},"subject":{"type":"string"},"body":{"type":"string"},"cc":{"type":"string"}},"required":["to","subject","body"]}}
User request: Email nora@example.com with subject "Confirmed" an... | null | Call email.send with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call email.send when the schema is provided for the shift lead",
"omits a required field for email.send",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for email.send calls with realistic optional-detail noise for the shift lead scenarios. |
TOOL-099 | Tool Calling | medium | Available tool schema: {"name":"weather.get_forecast","description":"Get weather forecast.","parameters":{"type":"object","properties":{"location":{"type":"string"},"date":{"type":"string"},"units":{"type":"string","enum":["F","C"]}},"required":["location","date"]}}
User request: Check the weather in Denver for 2026-06... | null | Call weather.get_forecast with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call weather.get_forecast when the schema is provided for a release note",
"omits a required field for weather.get_forecast",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for weather.get_forecast calls with realistic optional-detail noise for a release note scenarios. |
TOOL-100 | Tool Calling | medium | Available tool schema: {"name":"todo.add","description":"Add a task.","parameters":{"type":"object","properties":{"task":{"type":"string"},"due":{"type":"string"},"priority":{"type":"string","enum":["low","normal","high"]}},"required":["task"]}}
User request: Add a task to review the pull request by end of month, prior... | null | Call todo.add with only schema-supported arguments extracted from the request, clarifying only if a required field is genuinely missing. Account for the user's stated audience and keep the response clear and practical. | [
"does not call todo.add when the schema is provided for a volunteer coordinator",
"omits a required field for todo.add",
"adds arguments not present in the schema",
"asks for optional details instead of proceeding"
] | Failure reveals weak schema grounding for todo.add calls with realistic optional-detail noise for a volunteer coordinator scenarios. |
End of preview. Expand in Data Studio
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
p># maxxAgentV1test
Evaluation test set for stress-testing a sub-3B English language model on agentic tasks.
File: agentic_eval_2000.json
- Downloads last month
- 31