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

With no annotations, the description carries the full burden and does substantial work: it discloses the computation methodology, that price moves are stripped out, that the series cannot be backfilled, and that rows were banked on the day they existed. It omits return shape and any rate-limit or freshness details beyond the snapshot note, keeping it short of a 5.

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?

Three sentences, each earning its place: methodology, the no-backfill constraint, and the span_days caveat. It is front-loaded with the metric definition and free of filler, though the long first sentence and lack of visual structure keep it from a 5.

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 and no annotations, the description must stand in for return-value semantics, and it does explain the computed metric plus the meaning of span_days. It does not enumerate the other row fields (ticker, date, flow value), so it is strong but not fully self-contained for a data-retrieval tool.

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 100% and all four parameters (paid, since, ticker, tickers) are already documented in the schema, including the x402 payment flow. The description adds no syntax or selection guidance for these params, so the baseline 3 applies. It mentions span_days, but that is an output column, not a parameter.

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 resource and even its derivation ('spot bitcoin ETF creation/redemption flows, computed as change in shares outstanding times NAV'), which is far more precise than a restated name. It does not explicitly contrast itself with siblings like congress_trades or options_iv, but the domain is unmistakably distinct. Clear purpose, minor gap in sibling differentiation.

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 supplies important usage-relevant context (no backfill, issuer publishes only a current snapshot, span_days>1 indicates a gap), which implicitly tells the agent how to interpret stale or missing rows. However, it never states when to prefer this tool over alternatives or when paid delivery is warranted, so guidance is implied rather than explicit.

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