query_etf_flows_by_date_range

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

With no annotations provided, the description must carry the full burden. It indicates a read-only query operation, but does not disclose potential rate limits, authentication requirements, or edge-case behavior like empty results. It adds date-range context but lacks deeper behavioral details.

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?

The description is minimal and front-loaded with a clear one-sentence purpose, followed by a compact parameter list. No unnecessary words or repetition; every line adds value.

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?

Given the tool has an output schema (so return values are covered) and a low-complexity parameter set, the description is mostly complete. However, it does not mention whether the date range is inclusive or how to filter for both assets, leaving minor gaps.

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 0%, so the description compensates by specifying date format ('YYYY-MM-DD') and the allowed ticker values ('BTC' or 'ETH'). This adds meaning beyond the bare parameter names in the schema, though it does not clarify the default behavior when ticker is omitted.

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 clearly states the tool's function: 'Query historical ETF flows within a specific date range.' The verb 'query' and resource 'historical ETF flows' are specific, and the date-range scope distinguishes it from sibling tools like get_latest_etf_flows.

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 implies historical, date-scoped usage, which contrasts with the 'latest' in get_latest_etf_flows. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of full guidance.

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