{
  "title": "Design a Tool-use Schema for a Customer Support Agent",
  "description": "A ready-to-use prompt to design a tool-use schema for a customer support agent, producing a structured draft you can act on directly rather than a vague suggestion.",
  "category": "Agentic AI and Multi-Agent Systems",
  "tags": [
    "agentic-ai",
    "tool-use-schema"
  ],
  "templateContent": "Act as an AI agent architect. Design for reliability under partial failure: assume tools can time out, return malformed data, or be unavailable, and design accordingly. State explicit assumptions about the underlying model's capabilities rather than assuming a specific one.\n\nTask: Design a tool-use schema for a customer support agent.\n\nContext to use:\n- What the agent (or agent system) is trying to achieve: {{system_goal}}\n- Available tools or integrations: {{tools_or_integrations}}\n- Constraints and risk tolerance: {{constraints}}\n\nResponse format:\n1. Brief recommendation or approach\n2. Main deliverable, organized into clear sections\n3. Assumptions and unresolved questions\n4. Validation or quality checklist",
  "variables": [
    {
      "name": "system_goal",
      "label": "What the agent (or agent system) is trying to achieve",
      "type": "multiline",
      "required": true,
      "default": null,
      "allowedValues": null
    },
    {
      "name": "tools_or_integrations",
      "label": "Available tools or integrations",
      "type": "multiline",
      "required": false,
      "default": null,
      "allowedValues": null
    },
    {
      "name": "constraints",
      "label": "Constraints and risk tolerance",
      "type": "multiline",
      "required": false,
      "default": null,
      "allowedValues": null
    }
  ],
  "usageInstructions": "Fill in the context fields with your real project details, then review the assumptions section before acting on the output.",
  "limitations": "This produces a strong first draft, not a final deliverable; domain specifics should be verified before relying on it."
}