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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing about caching (only the schema mentions a cache via forceRefresh), rate limits, or required permissions. It also omits the maximum lookback window (8760 hours) and any indication of data granularity or result size.

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 front-loaded sentence with no filler; the provider, asset, and period dimensions all appear immediately. Nothing redundant is included.

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 annotations and no output schema, the description should at least sketch the return shape (time-series points, granularity, sample count) and caching/rate-limit behavior. The input side is fully covered by the schema, but the output and behavioral sides are left entirely to inference.

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 the schema already documents all five parameters including the enum lists and the period range. The description's only added phrasing ('over a period (in hours)') restates the schema, so the baseline of 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?

States a specific verb and resource: 'Get historical price data for an asset' from 'a specific oracle provider over a period (in hours)'. The word 'historical' implicitly separates it from get_oracle_price/get_consensus_price, but no sibling is named or explicitly excluded.

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 via the term 'historical' – an agent can infer this is the tool for time-series price lookups versus the spot-price siblings, but there is no explicit when-to-use, when-not, or alternative named. No prerequisites or provider-selection guidance are given.

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