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

Annotations cover safety (readOnly, idempotent, non-destructive) but say nothing about cost or paging. The description discloses the dual access model (0.01 USDC via x402 PAYMENT-SIGNATURE header versus a free API key, with auto-pay for x402 clients) and spells out that totals are computed over the full window even when results are paged — both are non-obvious behaviours an agent would otherwise get wrong.

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?

It is dense but front-loaded: scope first, then parameters, then the usage trigger, then access terms in a bracketed block. Nearly every clause earns its place, though the interpretation hints (inflows bullish, outflows bearish) are the least load-bearing sentence and could be trimmed.

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 still conveys the return shape: per-day rows newest first plus per-asset totals for the window. Combined with the documented paging, defaults, ceilings, and payment/auth requirements, an agent has everything needed to call it correctly on the first attempt.

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 already 100%, so the schema carries the parameter documentation and the baseline is 3. The description does add real meaning beyond it — lookback default 30 with a 3650 ceiling, limit 1-100, offset 0-10000, and the crucial note that totals always span the whole window regardless of paging — but it leaves the symbol value space open (schema only shows 'e.g. BTC or ETH' despite four supported assets).

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 opening clause names the exact resource (crypto spot ETF net flows per day), the covered assets (BTC, ETH, SOL, HYPE), the window, the sort order, and the aggregate totals returned. That is enough for an agent to separate it from near-neighbours such as get_smart_money_netflows or get_token_flows without opening the schema.

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 gives an explicit trigger sentence: use it when the user asks about ETF flows, institutional demand, or spot ETF activity, and adds the narrowing rule for symbol. It stops short of naming a competing sibling or stating a when-not condition, so it is clear context rather than full routing guidance.

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