get_stock_prices

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

No annotations are provided, so the description carries the full burden. It states the tool returns adjusted and unadjusted OHLCV data but does not disclose behavioral traits such as data source, rate limits, maximum date range, or whether data is cached.

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?

The description is concise: one sentence summarizing the tool, followed by a clear parameter list. Every line is informative, and there is no fluff.

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?

An output schema exists, so return values need not be explained. However, the description does not specify default behavior for optional parameters (e.g., what happens if start_date and end_date are null), or any limitations like exchange coverage. Given the number of siblings, more context would help.

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?

The input schema has no parameter descriptions (0% coverage), but the tool description compensates by listing each parameter and providing meaning: ticker (stock ticker), start_date (YYYY-MM-DD), end_date (YYYY-MM-DD), resample_freq (daily/weekly/monthly/annually). This adds value beyond the schema's type definitions.

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?

The description clearly states 'Get historical end-of-day stock prices with adjusted and unadjusted OHLCV data.' This is a specific verb+resource combination that distinguishes the tool from siblings like get_realtime_price (real-time) and get_intraday_prices (intraday).

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?

The description implies usage for historical daily data but does not explicitly state when to use this tool versus alternatives or provide any exclusions. No guidance on prerequisites or context.

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