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

Annotations already establish read-only/idempotent/non-destructive behavior, and the description adds meaningful extras: fresh inference instead of cached results, coverage beyond four assets, experimental status, no-investment-advice risk, and a $0.65 cost from credit balance. No contradiction with annotations.

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?

A single dense paragraph that front-loads the core function and then adds differentiators and cost/risk notes. Every clause carries information, though the bracketed payment/alternative note could be cleaner as a separate line or simplified.

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?

For a paid, experimental tool with no output schema, it covers pricing, freshness, scope, risk, and alternatives. The main gap is that it never explicitly states the returned artifact (chart versus data) or output format, leaving the agent to infer from the name and title.

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 high, so the schema already explains chain and interval enums/defaults; the description only adds general 'any token / any supported chain' context. It does not clarify token format (symbol vs. address), but the baseline for high schema coverage is 3 and no extra parameter detail was required.

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 concrete operation—real-time data retrieval and compute bundled with a live price forecast—and specific models and outputs (TimesFM 3.0 + Kronos with quantile bands). It also explicitly contrasts itself with sibling get_price_forecast, so an agent can distinguish the tool without opening the schema.

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?

It says when to choose this tool over the free get_price_forecast ('runs fresh inference and is not limited to four assets'), flags experimental/risk, and points to list_einstein_capabilities for free alternatives. This is explicit routing and exclusion guidance.

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