getCryptocurrencyHistoricalFullChart

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

Annotations already indicate readOnly, idempotent, and openWorld hints, which convey safety and repeatability. The description adds that it returns 'comprehensive end-of-day price data' but does not disclose additional behavioral traits like rate limits, pagination, or data range constraints.

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 with two sentences. The first sentence clearly states the purpose, and the second adds value by mentioning analysis use cases. No redundant or extraneous 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?

With no output schema, the description should describe the return data structure to aid model expectations. It mentions price data, trends, and volumes but does not specify fields (e.g., open, high, low, close, volume). Given the parameter simplicity, completeness is moderate.

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?

All three parameters (symbol, from_date, to) have descriptions in the input schema (100% coverage). The description does not add further meaning beyond what the schema already provides, so a baseline of 3 is appropriate.

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 'comprehensive end-of-day (EOD) price data' for cryptocurrencies, which specifies the resource and scope. It is distinguishable from sibling tools like getCryptocurrencyHistoricalLightChart by mentioning 'full' and EOD, but does not explicitly differentiate usage.

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 lacks any guidance on when to use this tool versus alternatives such as getCryptocurrencyHistoricalLightChart or other intraday data tools. No when-to-use or when-not-to-use context is provided.

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