Input Examples

Definition

input_examples is an optional array of example input objects on a tool definition that shows Claude concrete, well-formed invocations to improve tool-calling accuracy.

Key points

• Each example must validate against the tool's input_schema — an invalid example returns a 400.
• Token overhead: ~20–50 tokens (simple) up to ~100–200 tokens (complex nested).
• Not supported for server-side tools.
• Lives on the tool definition, alongside strict, defer_loading, cache_control, allowed_callers.

Why it matters for the exam

• Tested as a low-cost lever for improving tool-call reliability, distinct from strict (which enforces) — examples guide, strict guarantees.
• Netlight cites the 20–200 token range explicitly.

Common gotchas

• An example that doesn't match input_schema is a hard 400, not a silent skip.
• Cannot be used on server tools (web_search, web_fetch, code_execution, tool_search).

See also

• Tool Definition Schema
• Effective Tool Descriptions
• Strict Tool Use

Sources

• docs-tools-agents
• netlight-study-guide