US Spot Bitcoin & Ethereum ETF Flows

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world traits, so the bar is lower. The description usefully adds the auth/quota context (Pro API key needed for full history since launch) and the newest-first result ordering, which annotations do not convey.

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 sentences with no waste; the scope and ordering come first, followed by the one gating constraint. Nothing is redundant or buried.

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 adequately (daily total net flows, newest first) while covering the key access constraint. Pagination behavior and the include_funds trade-off are left unaddressed, keeping it short of fully complete.

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%, so asset, start_date, end_date, and include_funds are all documented in the schema itself. The description adds no parameter syntax or format detail beyond a general confirmation of what the dates bound, so the baseline 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?

Names a specific resource (daily total net flows in USD of US spot BTC or ETH ETFs) with the exact scoping constraint (between two dates, inclusive) and the ordering (newest first). This implicitly distinguishes it from siblings like get_latest_etf_flows and get_etf_flow_summary, which cover narrower or aggregated slices.

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?

The description states a prerequisite ('History since launch requires a Pro API key') but gives no explicit when-to-use vs alternatives guidance against get_etf_flow_summary, get_fund_flows, or get_latest_etf_flows. Usage is only implied by the date-range framing.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds useful scope context (US spot ETFs only, and precisely which aggregates are computed), but says nothing about freshness/lag, rate limits, or response shape, so it adds only moderate value beyond annotations.

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?

One front-loaded sentence: resource scope first, then the enumerated contents. Every listed aggregate earns its place because it tells the agent what it gets back without a call, and there is no filler or repetition of the tool name.

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?

There is no output schema, but the description enumerates the returned fields (latest day, 7d, 30d, MTD, YTD, cumulative since launch, streak, top 30-day inflow/outflow funds), which largely compensates. Minor gaps remain: no statement of data currency/as-of timing and no pagination or response-size expectations, though for a single optional-param read-only summary these are low-risk omissions.

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?

Single optional parameter with a two-value enum and 100% schema description coverage, so the schema fully documents it; the description only echoes the BTC/ETH asset split. Baseline 3 applies when the schema carries the parameter semantics.

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 (summary/overview of US spot BTC or ETH ETF flows) and enumerates the exact aggregates returned, so the agent knows this is a rolled-up snapshot rather than raw flow rows. It does not, however, name or contrast itself against siblings like get_etf_flows_by_date_range or get_latest_etf_flows, so the differentiation is inferable rather than explicit.

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?

No explicit when-to-use or when-not guidance is given. Usage is implied by the enumeration of aggregates (last 7/30 days, MTD, YTD, cumulative since launch, streak, top 30-day funds), which signals a reporting/dashboard use case, but the agent must infer the selection rule versus the date-range and latest-flow siblings.

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

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the safety profile is covered. The description adds the one thing annotations cannot express: an authentication requirement (free or Pro API key), which materially affects whether the call will succeed.

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?

A single front-loaded sentence with no filler: what is returned, the unit (USD), the cardinality (one ETF), the keying parameter (ticker), and the auth constraint. Every clause earns its place.

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 does its duty by naming the return payload (daily net flows in USD and a cumulative total). Combined with full schema coverage and annotations, only the sibling-routing guidance is missing, which is a modest gap for a two-parameter read 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%, so both parameters (fund and days) are already documented with format, bounds and defaults. The description's ticker examples (IBIT, FBTC, GBTC, ARKB, ETHA, FETH, ETHE) add a little breadth beyond the schema's single 'IBIT' example but no syntax or behavior the schema lacks, making the baseline 3 correct.

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 verb+resource+scope: daily net flows in USD plus a cumulative total for one ETF identified by ticker. It is easy to tell apart from get_etf_flow_summary or get_latest_etf_flows by the word 'one ETF' and the daily-series framing, but it never names the alternatives explicitly.

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?

The prerequisite 'Requires a free or Pro API key' is a useful routing signal, but there is no explicit when-to-use guidance against the four sibling tools. An agent must infer that a custom date range belongs to get_etf_flows_by_date_range and a point-in-time snapshot to get_latest_etf_flows.

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

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

Annotations cover read-only/idempotent/non-destructive. Description adds valuable access-tier behavior: without an API key only last 7 trading days with a 1-day delay, and include_funds requires a key. This goes beyond annotations by disclosing rate/access limits.

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 sentences, front-loaded with what the tool returns and ordering, then the API-key constraint. No wasted words.

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?

Covers scope, ordering, and access-tier limitations, which is important for a read tool with restricted access. Without an output schema, it would help to briefly mention the return shape (e.g., net flow values per day), but annotations and schema carry most of the load.

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%, so all parameters and enums are already documented. Description adds minor context (newest first) but does not expand on parameter semantics beyond the schema. Baseline 3 is appropriate.

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+resource: daily total net flows for US spot BTC/ETH ETFs, newest first. Clearly distinguishable from date-range and summary siblings by its 'latest/most recent' scope. Missing only explicit mention of the sibling alternatives.

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?

Implies use case (recent daily flows) but does not explicitly say when to use this vs get_etf_flows_by_date_range or get_etf_flow_summary. The API key caveat gives some context on access conditions, but no exclusions or alternative routing.

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

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered without description help. The description adds genuine context by enumerating what Pro unlocks (history since Jan 2024, same-day data, per-fund breakdown, CSV, higher rate limits), but it never says what the response actually looks like for an informational endpoint that has no output schema.

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?

A single front-loaded sentence with the actionable part ('how to get a free API key or upgrade to Pro') first and the detail list second. Nothing is wasted or repeated from structured fields.

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?

For a no-parameter static info endpoint with full annotation coverage, the description covers subject matter adequately. The only gap is that, absent an output schema, it doesn't hint at the response form (text guidance, link, or structured plan data).

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, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical feature list gives useful framing for what the returned guidance will cover.

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 names the resource concretely: instructions for obtaining a free API key or upgrading to Pro, plus what each tier includes. That is clearly distinguishable from the sibling flow-data tools, which return market data rather than onboarding/pricing information. It stops short of a crisp verb+resource framing but leaves no doubt about what the tool returns.

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?

There is no explicit 'use this when…' statement, but the nature of the tool (a static informational endpoint about API keys and Pro plans) makes the trigger self-evident, and no sibling overlaps with it, so the agent will not mis-route. No alternatives or exclusions are stated, keeping this at minimum-viable-plus.

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