get_price_history

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses key traits: raw/unadjusted data, newest-last ordering, CSV fallback for large pulls to protect context window, prices in Rial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each adding distinct value, front-loaded with core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Explains return format variations for CSV case, covers all three parameters, appropriate for tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond schema: days<=0 means full history, save_csv=True changes return format to file_path/summary/sample.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it provides daily OHLCV history for one symbol, raw/unadjusted, newest last. It distinguishes from siblings like get_quote or get_order_book.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on days<=0 for full history and CSV behavior for large pulls, but does not explicitly compare to alternatives like get_quote.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.