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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, which matches 'no market lookup' and reinforces that no external call occurs. The description usefully signals that the returned price is a recorded sample (potentially stale/demo), but says nothing about behavior on unknown symbols, missing records, or date-range limits.

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 tight sentence with the core action front-loaded and the 'no market lookup' qualifier at the end where it reads as a constraint. Nothing is wasted, though the extreme brevity leaves little room for the parameter detail this tool needs.

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?

An output schema exists, so return values need not be explained. But with 4 parameters at 0% schema coverage and only a passing mention of symbol/contract, the description leaves format for 'as_of_date', the meaning of chain vs wallet, and error behavior unspecified.

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 0% across 4 parameters, so the description must carry the semantics. It only hints at 'asset' (symbol) and 'chain'/'wallet' ('exact contract'), and gives no meaning for 'as_of_date' or the relationship between chain and wallet. Most parameters remain undocumented.

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 ('Read') and resource ('a recorded sample price') and narrows the source with 'by symbol or exact contract; no market lookup,' which lets an agent tell it apart from a live-quote tool. It does not explicitly differentiate from the holdings/wallet siblings, but those are clearly different resources.

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 market lookup' and 'recorded sample price' imply the usage context: this retrieves stored/demo data rather than fetching live prices. However, no alternative tool is named and no explicit when-not condition is stated, so the routing guidance is inferred rather than declared.

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