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 discloses the survivorship-bias-free nature, stitching from research-grade data to live bars, and the delisting record, which are important behavioral traits. It does not mention return format, pagination, or rate limits, but the core data behaviors are transparent.

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?

Two concise sentences that are front-loaded with the key purpose and immediately give usage guidance. No filler or redundant content.

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?

The description provides a rich portrait of data quality, time coverage, fields, and use cases, plus a clear alternative. However, the lack of parameter explanations and return structure is a gap, especially without an output schema. Still, it is more than adequate for tool selection.

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?

Schema coverage is only 25% (only ticker has a description). The description does not explain the format or semantics of start, end, or limit parameters, nor how the date range maps to the stitched periods. It adds context about the data content but not parameter usage, so it does not compensate for the low schema coverage.

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 it provides 'Survivorship-bias-free daily price history' with specific data fields (closes, total returns, volume, split factors) and time periods. It also distinguishes from alternatives by directing to /api/market/ohlc for intraday or recent-only bars.

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?

Explicitly says 'Call it for backtests and long-horizon charts' and gives an exclusion: 'for intraday or recent-only bars use /api/market/ohlc.' This gives clear when/when-not guidance.

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