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

With no annotations, the description carries the full burden, and it does disclose a lot: the 5-minute cadence, v3 with a v4 cross-check, USD liquidity, derived fields only (the raw reference quote is excluded), and coverage from 2026-10-23 that includes market-closed hours. It says nothing about rate limits, payload size at longer windows, or error behavior for an unknown symbol, which are the remaining behavioral gaps for a read-only series 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?

The description is dense and front-loaded: what the series is, then sampling and vendor details, then coverage window and audience. Every sentence adds information, with only mild redundancy in restating that coverage includes closed hours and in the final audience clause.

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 two-parameter, no-annotation, no-output-schema tool, the description covers what is returned, how it is sampled, and how far back it reaches. The main gaps are the default for hours and any note on how long a 720-hour response is.

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 0%, so the description has to compensate, and it partly does: 'for one symbol' makes clear that symbol is singular per call, and 'can reach back up to 720 hours' plus 'the window ends at the latest available sample' gives hours a unit, an upper bound, and an anchoring rule. What is missing is the default value for hours when it is omitted.

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 states a specific verb-and-resource: a time series of stock-token spreads for one symbol on chainId 4663, with concrete content (5-minute samples of pool price, liquidity in USD, spread vs. reference quote). It does not explicitly name the sibling rh-stock-spreads (presumably the current-snapshot version), so the difference from that near-twin is left implicit.

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?

It scopes usage to 'research and market-structure analysis of tokenized stocks,' which is context but not a when-to-use rule. There is no explicit guidance such as 'use rh-stock-spreads for the latest snapshot' or a statement of when not to use this tool, so an agent must infer the choice between the two spread tools.

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