Tools prompts
Template, every field annotated with what makes it work:
{
"name": "[verb_noun, e.g. search_orders: the action it performs, not the system it wraps]",
"description": "[3-5 sentences. This is the single highest-leverage string in your agent. Cover, in order: (1) what the tool does and what it returns, (2) WHEN to use it, (3) when NOT LLM Tool Definition Template
Write tool definitions agents actually use correctly: when-to-use descriptions, unambiguous parameters, and errors returned as data.
Agentadvanced
Extract structured data from the document below.
Extract exactly this JSON structure:
{
"[field]": "string. [WHAT IT IS + FORMAT + EXAMPLE, e.g. 'invoice number as printed, e.g. INV-2024-0031']",
"[date_field]": "string (YYYY-MM-DD) or null. [WHICH date this is; null if not stated]",
"[enum_field]": "one of: [\"option_a\", \"optionJSON Extraction Prompt
Extract structured data from messy text with a schema designed against the real failure modes: filled-in blanks, deep nesting, and inferred values.
Agentintermediate
[DESIGN a toolset / REVIEW my toolset] for an agent that does: [THE AGENT'S JOB, e.g. "manages our Linear tickets and posts standup summaries to Slack"] The underlying API/system: [WHAT'S AVAILABLE: the endpoints/operations that exist] The agent's real tasks: [5-10 CONCRETE TASKS IT WILL ACTUALLY PERFORM, e.g. "find all stale tickets ass
MCP Toolset Design Review
Design or review an agent toolset the Anthropic way: consolidated workflow tools, concise/detailed response formats, and errors that steer.
Agentadvanced