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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about caching behavior (even though forceRefresh exists), rate limits, or the range/shape of returned data. It only restates the data category.

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 essential scope (provider + period) comes early. It is appropriately sized, though it omits detail that would have earned a 5.

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 5-parameter getter with no annotations and no output schema, the description covers the core purpose and required inputs are well documented in the schema. However, the caching default, output format, and period cap are left for the agent to discover.

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 provider, symbol, period, chain, and forceRefresh. The description's 'over a period (in hours)' merely echoes the schema's 'Historical period in hours' without adding syntax or constraints (e.g., the 8760 cap).

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 (Get) and resource (historical price data) with scope qualifiers: a specific oracle provider, an asset, and a period. It is clear enough to distinguish from get_oracle_price or get_consensus_price, but it never names siblings to sharpen the boundary.

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?

No when-to-use or when-not-to-use guidance is given. With siblings like get_oracle_price, get_consensus_price, and oracle_watch_history, the agent has to infer that this is the historical/time-series variant rather than being told.

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