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

Since no annotations are provided, the description carries the full burden of disclosure. It explains key behavioral aspects: optional time range, default to latest price when no range is given, Unix millisecond timestamps, and slash-separated currency format. This goes beyond the raw schema and gives users essential operational context.

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 four compact sentences, front-loaded with the primary action ('Fetches historical crypto price data'). Every sentence provides useful information, with no redundancy or filler.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description covers the main usage patterns: fetching historical ranges, getting the latest price, timestamp units, and currency format. It does not describe the return structure or pagination behavior, but the schema already explains pagination_key and limit, and the absence of an output schema may make this acceptable.

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 100%, so the schema already documents all five parameters. The description reinforces the currency format and timestamp units, but these details are also present in the parameter descriptions. It adds some value by explaining the interplay between time range parameters and the limit default, but does not significantly expand on the schema.

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 the tool fetches historical crypto price data from Chainlink, specifying a distinct resource (Chainlink prices) and behavior (historical data with optional time range). This distinguishes it from sibling tools like dome_binance_prices or dome_market_price.

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 provides clear context on when to use the tool: for historical crypto prices from Chainlink, with optional time ranges, and notes the behavior when no time range is given (returns most recent price). It does not explicitly mention alternatives or exclusions, but the Chainlink source makes its purpose distinct.

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