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

With no annotations at all, the description carries the full burden. It does disclose a genuinely important behavioral trait that no structured field covers: access requires either a 0.01 USDC x402 payment via PAYMENT-SIGNATURE header or an API key, and x402-capable clients auto-pay. It says nothing about the lookback window, update cadence, or whether flows are daily/aggregate, which matters for interpreting the result.

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?

Two tight blocks: the metric definition and its interpretation first, then the access/payment note in brackets. Front-loaded and waste-free. The bracketed payment paragraph is longer than the substantive content, but it is operationally necessary given no annotations cover it.

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?

No output schema and no annotations, so the description must carry everything. It conveys what the metric is and how to read it, but omits the shape of the response (per-asset breakdown? time series? latest snapshot?) and the time horizon covered. For a no-parameter data tool those are the remaining unknowns an agent would want.

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?

The tool takes zero parameters (empty object schema), so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies a fixed-scope, no-argument fetch rather than leaving the agent hunting for filters.

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 resource and metric ('Crypto ETF net flows -- institutional inflows and outflows for spot BTC and ETH ETFs'), which is unambiguous against siblings like get_smart_money_flows, get_token_flows and get_stablecoin_metrics. It also adds an interpretive frame (net inflows = bullish, outflows = bearish) that tells the agent what the number means.

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?

Explicit trigger conditions are given: 'Use it when the user asks about ETF flows, institutional demand or spot ETF activity.' That is clear routing guidance. It does not name an alternative (e.g. get_smart_money_flows) for the overlapping 'institutional demand' phrasing, so exclusion guidance is absent.

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