getUnadjustedChart

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds that the tool returns open, high, low, close prices and volume, which is helpful but minimal beyond annotations. No mention of side effects, auth needs, or rate limits.

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 two sentences, front-loading the main purpose. It is efficient with no fluff, though slightly verbose with repetitive 'without split-related changes'. Could be tighter but effectively concise.

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?

No output schema exists, so description must explain return data. It mentions OHLCV and volume, which is adequate for a chart tool. However, it lacks details on date range behavior (e.g., pagination, limits) and does not clarify that from_date and to are optional. Adequate but not complete.

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?

Input schema has 100% coverage with descriptions for all three parameters (symbol, from_date, to). The description repeats the unadjusted nature but adds no new meaning or format details beyond the schema. Baseline 3 is appropriate as description does not compensate.

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 the tool retrieves unadjusted stock price data, specifically 'without adjustments for stock splits,' and mentions the API source. It uses specific verbs ('access') and resource ('Unadjusted Stock Price Chart'), effectively distinguishing it from adjusted chart tools.

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 use when unadjusted data is needed, but lacks explicit guidance on when not to use or alternatives (e.g., 'Use this for raw data; for adjusted data use getDividendAdjustedChart'). No exclusions or context provided.

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