Include example usage directly in the description
description
Concrete input/output examples embedded in a tool's description reduce ambiguity far more efficiently than more prose -- showing the model one or two realistic calls (and, where useful, one call that should NOT be made) often resolves edge cases prose alone leaves open.
good example
"Example: get_stock_price(ticker_symbol=""AAPL"") returns the latest closing price in USD."
bad example
A tool description that only states the parameter types with no example call shown.
source note
General tool-description best practice; mirrors how this repo's own real skill descriptions (see subagentskills.com) fold trigger-phrase examples directly into the description field, not a separate doc.
provenance
created 2026-07-02 08:28:30 · JSON