getCryptocurrencyHistoricalFullChart

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that by disclosing data granularity (end-of-day) and that trading volumes are included, but says nothing about pagination, rate limits, maximum history depth, or what happens when from_date is omitted.

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 sentences, front-loaded with the core capability and data granularity. The second sentence is partly marketing filler ('inform strategic decisions') but does earn some place by naming the analysis dimensions (trends, market movements, volumes) the data supports.

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 and no annotations covering data shape, the description should explain what a record contains (OHLCV bars, one row per day) and whether the date range is optional. It hints at price and volume but leaves the return shape and default date behavior unspecified, which matters for a three-parameter historical data tool.

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 description coverage is 100%, so symbol, from_date and to are already documented with formats and an example. The description adds only a loose implication that a date range governs the result, with no additional syntax, default, or boundary behavior beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource: retrieve comprehensive end-of-day (EOD) price data for cryptocurrencies over the full history. The word 'Full' plus 'end-of-day' implicitly separates it from the intraday siblings (getCryptocurrency1MinuteData, 5Minute, 1Hour) and from getCryptocurrencyHistoricalLightChart, but the distinction is never made explicit, so an agent must infer it.

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?

Usage is only implied through the phrase 'Analyze long-term price trends,' which signals long-horizon analysis rather than intraday work, but the description never names the LightChart or intraday alternatives or states when not to use this tool. An agent could reasonably pick this over getCryptocurrencyHistoricalLightChart with no guidance on the trade-off.

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