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

Annotations only say readOnly and openWorld; the description layers on genuinely new behavioral facts: the upstream source is Nasdaq.com because Stooq blocks automated downloads, results are newest-first, $0.002 USDC per successful call via x402 on Base/Solana/Arc, and failed calls are free. That is exactly the payment/auth and failure-cost context an agent needs before invoking a paid endpoint.

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 what is returned, then constraints, then cost. Every sentence carries information, though the source-attribution clause ('Stooq blocks automated downloads') is slightly tangential to the calling decision.

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 an output schema present, the field list is a bonus rather than a necessity, and the paid-call mechanics, sort order and hard limits are all covered. The one gap is pagination: it says max 1,000 rows per call but never tells the agent to issue successive from/to windows to cover longer histories.

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 baseline is 3, but the description adds a real constraint absent from the schema: the 10-year lookback ceiling on the from/to pair and the 1,000-row cap implied by limit. It does not clarify assetClass/ticker interaction (e.g. index symbols), which keeps it below a 5.

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+resource and enumerates the exact returned fields (date, open, high, low, close, volume) plus the asset universe (US stock, ETF or index) and sort order. It is clear and self-contained, but never names a sibling such as finance_yahoo_finance or finance_alpha_vantage_public, which also serve historical price data, so the agent gets no explicit routing signal.

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?

Gives concrete usage constraints — any range up to 10 years back, max 1,000 rows per call — which implies how to scope requests. However there is no statement of when to prefer this over the many overlapping finance/crypto price siblings, nor any prerequisite note such as needing a funded x402 wallet before calling.

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