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

Goes well beyond the readOnly/idempotent annotations: 15-minute refresh cadence, off-hours value freezing, premium/discount versus underlying, the `excluded` naming with reasons, uncovered tokens being counted not named, per-rail coverage counts, and pay-per-call pricing. These are exactly the behaviors an agent needs before invoking.

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?

Dense but front-loaded: the core purpose and rails come first, with behavioral detail following. Every sentence carries information, though the run-on middle section could be split for readability.

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 no output schema, the description compensates by explaining the return shape (ranked gainers/losers vs prior NYSE close, coverage counts, `excluded` reasons, uncovered counting). Combined with the payment flow, an agent has enough to call correctly.

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?

Only one parameter (x_payment) with 100% schema coverage that already explains the challenge/retry protocol. The description adds pricing context ($0.003 USDC via x402, free allowance preservation) that the schema does not, though it does not restate the omit-to-get-challenge mechanics.

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?

Opens with a specific verb ('Read') and a precisely scoped resource: day movers among tokenized US stocks and ETFs across two named rails (Robinhood Chain 4663, Base B20), keyed by token address. This is clearly distinguishable from the broad sibling otto_tokenized_equities, which covers listings rather than movers.

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 states the context ('Market context only; not a recommendation') and the paid-access condition, plus the x402 retry flow. But it never names an alternative tool or says when an agent should prefer this over otto_tokenized_equities or otto_equity_intel. Usage is implied rather than routed.

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