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

With no annotations, the description carries the full load and does well: it discloses cost and auth paths (0.02 USDC via x402 PAYMENT-SIGNATURE, or API key with no per-call charge), symbol normalization (native ETH read as WETH), chain-existence and stablecoin availability constraints, and that results are paginated. It stops short of describing what a 'flow record' contains or how the upstream pass-through filters behave.

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 the core purpose and scope, then the sibling routing, then availability caveats, then a bracketed access note. No sentence is redundant; the payment line is dense but carries decision-relevant information for an agent choosing whether to call.

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 9-parameter read tool with no annotations and no output schema, the description covers scope, exclusions, cost/auth, and routing, which is most of what an agent needs. The only shortfall is that the nested filters/order_by pass-through parameters and the shape of returned flow records are left to the upstream provider.

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 the baseline is 3; the description adds real meaning on top by constraining 'label' to a single wallet category and framing date_from/date_to as an explicit required window rather than optional fields. It leaves the nested 'filters' and 'order_by' pass-through objects unelaborated, which is the remaining gap.

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 (paginated historical flow records) plus the exact scope: one non-stablecoin token, explicit start/end dates, optional single wallet label. It explicitly names the sibling it is not (get_smart_money_flows) and why, so an agent can distinguish the two without opening either 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 an explicit positive condition (date-range records or pagination) and an explicit negative/alternative condition (trailing-window net USD flows plus wallet counts across categories → get_smart_money_flows). It also states an exclusion ('Not available for stablecoins') and a precondition (the token must exist on the requested chain).

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