{
  "practice": {
    "id": "prc_descriptive_param_names",
    "title": "Give parameters descriptive, self-explanatory names",
    "category": "naming",
    "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.",
    "example_good": "`ticker_symbol: string` with description \"e.g. AAPL, TSLA\"",
    "example_bad": "`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.",
    "created_at": "2026-07-02 08:28:30",
    "cite_as": "https://subagentdescriptions.com/api/practices/prc_descriptive_param_names"
  }
}