Give parameters descriptive, self-explanatory names
description
Parameter names are part of the model's only signal for what a field means -- prefer a clear, specific name (and a short description on the parameter itself, not just the top-level tool description) over a short but ambiguous one.
good example
`ticker_symbol: string` with description "e.g. AAPL, TSLA"
bad example
`t: string` with no description
source note
General JSON Schema / function-calling best practice, applicable across MCP tool schemas and Anthropic tool_use blocks alike.
provenance
created 2026-07-02 08:28:30 · JSON