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

Goes well beyond the annotations (which only cover read-only/idempotent/safe) by disclosing data-availability behavior: US trading days only, no weekend/holiday entries, and a one-session publication lag for the latest day. That latency and gap information materially affects how an agent should call and interpret the tool.

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?

Front-loaded with purpose, then usage, then constraints and scope; no filler sentences. The opening sentence is dense with three comma-separated output clauses, which slightly reduces scannability but every clause carries information.

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 carries the return-value burden and does so: it names the per-fund breakdown, the 5-day/30-day sums, and the daily totals series. Data gaps (weekends/holidays) and freshness lag are also covered, so nothing needed to call it correctly is missing.

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 100% for the single 'days' parameter, so the schema already documents type, bounds (1-30) and default 10. The description restates the cap ('up to 30 recent daily totals') and default without adding new semantics, so the baseline of 3 applies.

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 verb and resource ('Net daily flows into US spot Bitcoin ETFs in USD millions') and enumerates the exact outputs: per-fund split, 5-day/30-day sums, and up to 30 daily totals. The 'US spot' qualifier distinguishes it from the sibling get_australian_bitcoin_etfs without needing to open a 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?

Gives explicit triggering conditions ('Use this when the user asks about ETF inflows or outflows, institutional demand or a specific fund's flow') and a scope exclusion ('Flows only, not fund holdings or prices'). It does not name the sibling alternative (e.g. Australian ETFs) for non-US requests, so routing across siblings is only implied.

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